| RE: [cosmos-dev] Security in the COMOS DC |
|
Check out https://issues.apache.org/jira/browse/MUSE-242.
I’m hoping that we can use this. It’s currently assigned to Balan
(our newest committer!), so maybe we can get an update from him. ;-) Cheers, Joel The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
Dear All, Not that I have been shy in creating
enough trouble these days…. J Here is one more… There is ONE more issue that we have
touched on in the past, but it keeps coming back as part of our use case
discussions: Security…. Some very raw thoughts / comments
that have come up in this regard (advance warning: some of these questions are
out there…): 1. How should the COSMOS DC enforce
security? What specific architectural entities covered by security? 2. Can I use my own existing SSO
product in conjunction with the COSMOS DC framework? 3. I will secure my Data Adapters; am I
also supposed to secure the Data Managers? 4. I assume that the COSMOS DC will
secure the Management Domain and the Brokers, right? 5. How will you prevent someone from
putting a sniffer on a Data Manager? 6. Does WS-Security apply (or not
apply) to this effort? 7. I may someday work with products
from the competition via the COSMOS DC. While I see the value in my
product working in conjunction with my competitors’ at a customer site,
how do I ensure that my critical / proprietary data does not get exposed? 8. Should there be (an) enhancement
request(s) for Security? Thanks, Jimmy Mohsin +1-609-635-1703 |