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

 


Help: OASIS Mailing Lists Help | MarkMail Help

cti-cybox message

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


Subject: Re: [cti-cybox] CybOX 3.0: Address Object Refactoring


On 29.10.2015 15:16:39, Kirillov, Ivan A. wrote:
> 
>   1. Where should CybOX data validation occur? Should it happen at
>   the instance generation level or at the consumption level, or
>   perhaps both?
> 

As you say, this deserves its own discussion thread but my strong
feeling is that validation should happen at both the producer and
consumer side.

If I'm a producer and I'm sending you invalid data, that damages my
reputation.

If I'm a consumer and I'm attempted to process data which I haven't
first validated, well, then I'll get what I deserve.

If we're talking in terms of a future iteration on python-cybox, then
I think it makes sense to enforce this in code. But I don't think it
needs to be stipulated in the standard, because it's clearly in the
best interest of *both* producers and consumers to perform validation.

-- 
Cheers,
Trey
--
Trey Darley
Senior Security Engineer
4DAA 0A88 34BC 27C9 FD2B  A97E D3C6 5C74 0FB7 E430
Soltra | An FS-ISAC & DTCC Company
www.soltra.com
--
"It is always possible to aglutenate multiple separate problems into a
single complex interdependent solution. In most cases this is a bad
idea." --RFC 1925

Attachment: signature.asc
Description: PGP signature



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