Re: [cti] versioning

["Jordan, Bret" <bret.jordan@bluecoat.com>]

Some may want feedback and others may not.  We have talked about adding a URL fields in the information source object so that you could lookup their TAXII server in DNS.  Just FYI.

Thanks,

Bret

Bret Jordan CISSP

Director of Security Architecture and Standards | Office of the CTO

Blue Coat Systems

PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050

"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg." 

On Feb 17, 2016, at 18:53, John-Mark Gurney <jmg@newcontext.com> wrote:

Aharon Chernin wrote this message on Mon, Feb 15, 2016 at 14:13 +0000:

If we want the community collaborating on intelligence, then we need to either allow for suggesting of updates to the original object, some sort of derived intelligence relationship, or both.

I am a fan of both approaches. Only the author can revision the original document. However, anyone else can create a new object with a relationship between the new and old objects and the type of “suggested-update”. A suggested-update could include revised facts or even a recommendation for revocation.

I like the idea of suggested-update.  We should add an optional field
to the information-source object that provides a URL that someone can
submit updates too.  If we don't, then it becomes harder to share
information.

Obviously, it could become a spam trap, but if the org says, only signed
suggestions are allowed, and maybe some mechanism for proving your
signature isn't a spam bot, this could be a powerful feature...

--
John-Mark

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail