Object ID format - Proposal

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

Here is my proposal:

• STIX uses a simple ID of [object-type]::[UUID] for all objects.
• For all top level objects, an InformationSource SHOULD be included

Use Cases 1:

1. John sends me a relationship objects of:
1. indicator::uuid and
2. malware::uuid
2. I do not have indicator::uuid or malware::uuid
3. But the relationship object has a InformationSource that points back to John
4. I go ask John either via TAXII or out-of-band methods can you tell me more about indicator::uuid and malware::uuid
5. John can respond with a few difference answers:
1. Yes, here is the information source for those objects, go ask them
2. No, I can not tell you
6. If yes, and say the indicator was produced by Jason and I have a contract with Jason to talk to his TAXII server or to call him on the phone and get more information, I can then use the ID to talk to him

Doing this will allow for all of the use cases we have discussed.  It allows for the use case that everyone can talk to everyone.  It allows for the use case of anonymous none attributed data.  It also allows for the use case of proxied content.  

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." 

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