OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cti-stix message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [cti-stix] [+1]'s

 This relates to Sightings so presume it is in the narrowed focus group of topics. 

(1) Discourse on the definition of a "[+1]"?

Not sure what the objection(s) are to the approach suggested a number of times in the past:  "Sharing my sightings, findings, assertions/basis for same are in fact "my vote""

Given an "RFI" construct (and or RFI COA) , then "I" can respond with as little or as much detail as I wish.  This approach supports the CTI community CORE DOCTRINE:  "One way to do "'stuff'" while supporting the "[+1]" Minimalism Camp.  

For "me" I'll share what I saw, when, who it was targeting, what the C2 NetFlow patterns where, the Malware Samples, my analysis of the DNS Domain Registration correlations to prior Campaigns, and perhaps some PCAPs of Exfil  from my HoneyNet as well.  This allows both Camps/Factions to have "their way"

I would like to circle back on this to understand the objections.

(2)  What is the alternative to the proposed "Source Pathway Traceability" Construct/Methodology?

How does one "send" their "[+1]" package back to the original source? 

(3)  How does the Source track/tally these "votes"  Does the Source share the tallied results/findings?

Patrick Maroney

From: <cti-stix@lists.oasis-open.org> on behalf of Jerome Athias <athiasjerome@gmail.com>
Date: Tuesday, November 10, 2015 at 9:07 AM
To: John Wunder <jwunder@mitre.org>
Cc: Jason Keirstead <Jason.Keirstead@ca.ibm.com>, Trey Darley <trey@soltra.com>, Terry MacDonald <terry@soltra.com>, Sean Barnum <sbarnum@mitre.org>, "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org>
Subject: Re: [cti-stix] [+1]'s

That's a potential approach for Incident.
Otherwise, what about "Under investigation" (for Opened) and potentially "False positive" as potential IncidentStatus enumeration items?

On Tuesday, 10 November 2015, Wunder, John A. <jwunder@mitre.org> wrote:
I like “sighting” and “confirmation”.

While we’re naming things, I’ll also suggest renaming “Incident” to “Investigation” and having some sort of field (status?) to denote whether it’s a true “incident” (per the definition of whoever is creating the construct, I guess)

On Nov 10, 2015, at 6:32 AM, Jason Keirstead <Jason.Keirstead@CA.IBM.COM> wrote:

If we do create two constructs, I would humbly suggest that we try to come up with a more distinct term for this, otherwise discussing "sighting" and "citation" in conversation will result in endless confusion.

Its already had enough for me to communicate the difference between an indicator and an observable to people :)

Jason Keirstead
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

<graycol.gif>Trey Darley ---11/10/2015 10:18:30 AM---On 06.11.2015 22:58:44, Terry MacDonald wrote: >

From: Trey Darley <trey@soltra.com>
To: Terry MacDonald <terry@soltra.com>
Cc: Jason Keirstead/CanEast/IBM@IBMCA, "Barnum, Sean D." <sbarnum@mitre.org>, "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org>
Date: 11/10/2015 10:18 AM
Subject: Re: [cti-stix] [+1]'s
Sent by: <cti-stix@lists.oasis-open.org>

On 06.11.2015 22:58:44, Terry MacDonald wrote:
> 1. +1 = “I have seen this too” (A sighting)

I would call this a *sighting*.

> 2. +1 = “I agree with your assertion” (Agreement with an assertion
> made)

I would call this a *citing*. (Perhaps "citation" to minimize

Trey Darley
Senior Security Engineer
4DAA 0A88 34BC 27C9 FD2B  A97E D3C6 5C74 0FB7 E430
Soltra | An FS-ISAC & DTCC Company
"In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away."
--RFC 1925
[attachment "signature.asc" deleted by Jason Keirstead/CanEast/IBM]

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]