Big Data security & privacy
NIST S&P Version 2: The Big Two
Reality Check in Apache Ecosystem
Implications | Directions
Security & Privacy (& Management)
What is a security fabric?
Big Data S&P Fabric
“Fabric” Not Original, Which is Good
Use Case: Image Processing
Big Data: Risks & Solutions
Audit to Provenance
Existing Models
Coordination
Concepts in Play
Definitions: Privacy and Security
Privacy by Design

Reality Check in Apache Ecosystem

Secure, Multi-Tenant Deployment Much like the early days of Hadoop, Apache Storm originally evolved in an environment where security was not a high-priority concern. Rather, it was assumed that Storm would be deployed to environments suitably cordoned off from security threats. While a large number of users were comfortable setting up their own security measures for Storm, this proved a hindrance to broader adoption among larger enterprises where security policies prohibited deployment without specific safeguards. Yahoo! hosts one of the largest Storm deployments in the world, and the engineering team recognized the need for security early on, so it implemented many of the features necessary to secure its own Apache Storm deployment. Yahoo!, Hortonworks, Symantec, and the broader Apache Storm community have been working on integrating those security innovations into the main Apache code base. That work is nearing completion, and is slated to be included in an upcoming Apache Storm release. Some of the highlights of that release include: Kerberos Authentication with Automatic Credential Push and Renewal Multi-Tenant Scheduling Secure integration with other Hadoop Projects (such as ZooKeeper, HDFS, HBase, etc.) User isolation (Storm topologies run as the user who submitted them) In the future, you can expect to see further integration between Apache Storm and security-focused projects like Apache Argus (formerly XA Secure).