Open Adithya-adi-Menon opened 2 months ago
HI @Adithya-adi-Menon, thanks for the submission! Having an externally accountable system that can't be edited can be a great protection against an attacker maliciously redacting information about an attack, but it can also cause challenges if the original owner of the logs needs to redact sensitive data or personally identifiable information. We're a little bit concerned about putting such info on a public network like Filecoin, even encrypted.
Can you explain more about what you're planning to do to sanitize and de-anonymize the logs to make sure security keys, personal information, and other sensitive data are not included in the published logs accidentally? Do you have a specific subset of logs or applications you're planning to target that are lower risk? For example, anonymized bug reports and stack traces would be less sensitive than something like API or user access logs.
Hi @ErinOCon, Thank you for your insightful feedback regarding the handling of sensitive data in our decentralized log management system. Your concerns are valid, and I appreciate the opportunity to clarify our approach.
Data Sanitization and Anonymization Strategies Log Filtering: Prior to the storage of logs on our decentralized platform, we will implement a rigorous filtering mechanism. This will involve a comprehensive analysis to identify and exclude sensitive data elements, such as personally identifiable information (PII) and security credentials. We will establish clear guidelines for determining what constitutes sensitive information, balancing the need for security with the utility of the logs.
Anonymization Techniques: We intend to employ advanced anonymization techniques, including tokenization and hashing. For example, user identifiers will be replaced with pseudonymous tokens, effectively obscuring individual identities while retaining the log’s usefulness for analysis. However, while these methods can enhance privacy, they may introduce complexities in correlating data for legitimate troubleshooting, as the original context may be lost.
Access Control Mechanisms: Although logs will be stored on a decentralized network, we will incorporate strict access control mechanisms via smart contracts. This will ensure that only authorized personnel can access specific subsets of logs, thereby safeguarding sensitive information. The challenge here lies in maintaining a balance between accessibility for legitimate users and preventing unauthorized access.
Targeted Applications and Log Types Initially, our focus will be on log types that present a lower risk in terms of sensitive information exposure. Examples include:
Anonymized Bug Reports: These can provide critical insights for development and security teams without compromising user confidentiality. The downside is that, if not properly managed, even anonymized reports could inadvertently reveal patterns that lead to identification of individuals.
Stack Traces: When anonymized, stack traces can significantly aid in debugging processes while minimizing exposure of operational details. However, reliance on these logs can sometimes lead to oversights in more sensitive operational contexts, necessitating a careful review process.
Continuous Evaluation and Improvement We will institute a periodic review process to evaluate the types of logs being collected and their associated risks. This will allow us to adapt our data sanitization practices based on user feedback and evolving security landscapes.
In conclusion, our strategy integrates a combination of proactive data sanitization, targeted logging practices, and robust access controls to effectively mitigate risks associated with storing logs on a decentralized network. While these methods enhance security and privacy, they also introduce potential challenges that we will continuously address to ensure a reliable and secure logging solution.
Please feel free to reach out if you have further questions or require additional details on any specific aspect!
Hi @Adithya-adi-Menon, I hope you are doing well! Your project is currently shortlisted as a review candidate. If we have any remaining questions, we will contact you on this thread.
If you have questions on your end, please feel welcome to be in touch at grants@fil.org. We would be happy to connect.
Hello @ErinOCon
Thank you for the update! I appreciate the opportunity to have my project shortlisted for review. If there are any further questions or clarifications needed from my side, please don’t hesitate to reach out.
In the meantime, I will stay available for any follow-up communication. Looking forward to the next steps.
Best regards, Adithya Menon
Open Grant Proposal: Decentralized Cybersecurity Log Management
Project Name: Decentralized Cybersecurity Log Management
Proposal Category: Storage
Individual or Entity Name: Adithya Menon Sanil
Proposer: adithya-adi-menon
Project Repo(s): https://github.com/Decentalized-Log-Management/Decentalized-Log-Management
Do you agree to open source all work you do on behalf of this RFP under the MIT/Apache-2 dual-license?: Yes
Project Summary
Cybersecurity professionals face increasing challenges with managing and analyzing vast amounts of security logs generated by various systems. Traditional centralized log management solutions are prone to single points of failure, data tampering, and security breaches. Our project aims to address these challenges by developing a decentralized cybersecurity log management platform utilizing IPFS, Filecoin, and the Filecoin Virtual Machine (FVM).
The platform will leverage IPFS for immutable and distributed storage of security logs, ensuring data integrity and availability. Filecoin will be used to incentivize storage providers and ensure long-term data retention. Additionally, FVM will facilitate smart contract-based automation of log management tasks, such as integrity verification and access control. This decentralized approach will enhance the security, resilience, and transparency of log management, addressing critical pain points in current solutions.
Impact
This proposal addresses several key issues in cybersecurity log management:
Outcomes
The final deliverables for this project will include:
Success will be measured by:
Adoption, Reach, and Growth Strategies
Our target audience includes cybersecurity professionals, IT departments, and organizations dealing with sensitive data. This audience is substantial, with increasing demand for secure and reliable log management solutions.
To engage this audience:
Development Roadmap
Milestone 1: Project Planning and Design (October 2024 - November 2024)
Milestone 2: Decentralized Log Storage Implementation (December 2024 - February 2025)
Milestone 3: Incentivization and Smart Contract Integration (March 2025 - May 2025)
Milestone 4: User Interface and Testing (June 2025 - August 2025)
Total Budget Requested
Maintenance and Upgrade Plans
Post-launch, we will focus on:
Team
Team Members
Team Member LinkedIn Profiles
Relevant Experience
Our team has extensive experience in cybersecurity, decentralized systems, and blockchain development. We have successfully completed similar projects, including decentralized storage solutions and cybersecurity tools, making us well-equipped to deliver this project.
Team code repositories
Additional Information
We learned about the Open Grants Program through hackathons.
For discussing the grant agreement and the next steps, please contact us at adithyamenon21@gmail.com.