The goal is to allow access to data, appropriate to the individual’s need and level of trust/vetting, without compromising confidentiality. Members of the CSI2 working group are asked to review the “Proposed Sharing/Privilege Outline” on the wiki and provide any feedback or concerns to Brian.
There was a discussion about whether REN-ISAC or CSI2 has a stance on stripping out local traffic prior to submitting shared darknet data to REN-ISAC. The original intent was that institutions would only report darknet traffic that originates from outside of the institution. It is expected that almost all shared darknet participants will do so.
Doug said he would be interested in whether contributions are coming from behind ACLs or firewalls, because that would affect how REN-ISAC reports aggregate numbers. There was also interest in have REN-ISAC provide port information and information about ASNs – some ASNs seem to dominate multiple log-in attempts.
Brian reviewed the table on the wiki page that indicates which types of data would be accessible by different user groups. For example, shared darknet participants would have access to all four types of data. As the document stands, REN-ISAC members could not access unfiltered source data, but could see everything else. But does that make sense? Doug suggested the data be open to REN-ISAC members and those providing shared darknet data, provided that they have a reasonable justification for why they need the data. REN-ISAC would still provide aggregate analysis reporting and would notify .edu’s of any potentially compromised machines within their control, regardless of whether they are REN-ISAC members.
But would this make it less likely that people would use the data? Perhaps any REN-ISAC member should have access to the data, even in a filtered way.
[AI] {Brian} will add a proposal to the wiki regarding some sort of gateway requirement for data sharing.
**Hashing**
Chris has a part-timer for the summer building code to do some of the data hashing. Phil has the write-up and diagram for the hashing proposal – email him if you would like a copy.
**RENOIR**
Phil has started the coding for revisions to RENOIR. He has outsourced the SOAP server development to a student as a summer project. In the meantime he is developing the web interface and database.
**Funding Source**
Doug reviewed a grant announcement that might be a fit with RENOIR or other CSI2 projects. There is a June 27 deadline for a five-page paper describing a project and a September 17 deadline for full proposals. The grants vary from 12- to 36-months.
[AI] {Chris} will place this on the agenda for the next call.
The next call is June 7 at 2:30 pm (EDT)