[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti] CTI TC Adoption and Interoperability SCs
I understand what you are saying, but that is way too complex... Think about this from a Product Manager standpoint, not an academic stand point, further the whole point of doing this is for product managers and consumers. Product Managers are going to ask "how much of this do I need to implement to be compliant and do what my customers are asking for". Customers want some level of assurance that a vendor has actually implemented some level of support so they can make buying decisions and interoperability decisions. Just like Common Criteria, vendors will start using their level of support as a stick to say they are better than some other vendor, which is good for us. This means, that more and more vendors will support more and more of STIX. <soapbox> Yes I know we are also talking about CyboX and that CybOX can stand on its own and can be used by other things. However, in the real world when we get across the chasm and gain of mass adoption, people will not care, and it will referred to as just STIX. Because from the outside, assuming you did not know anything about it or its development, you would ask yourself WHY is it called two different things when it is just the same thing. </soapbox> We need a very simple set of "line in the sand" markers of support. When you look at the list of products that claim they support STIX, right now we have NO idea what that means. Nor does any consumer or user have any idea what that means. Linksys for example, could add the ability in their interface for their home router to see the configuration of the admin page in STIX XML and they could then claim, legally, on all of their documentation that they are STIX compliant. Building a simple set of "line in the sand" markers will also drive adoption, especially if the first level is relatively easy to get to. This will be something that a product manager can safely commit to his/her board of directors. 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]