Inrupt’s Post

Immuta’s approach to data security at sale 🚀 At the AWS Financial Services Symposium, #theCUBE sat with Chris Brown, the public sector CTO at Immuta, to learn about their approach to ensuring data security at scale through data platform integrations. “In the past, we created proxy patterns back into our data systems. The problem with those is that as people go through there, you have to scale those systems out and your data platform at the same time. Doing that is a massive chore and something that no one wants to do,” explained Brown. “At Immuta, we've actually integrated into those data platforms. Now, we become the policy authoring and the policy decision points, and we push those decisions down into those compute platforms where they become the policy enforcement point. This is great because everyone wants to do these self-service analytics,” he added. “Now, we're actually giving people the true power to be able to bring in whatever business intelligence tool they want and run whatever model they want. They can access that compute platform because those policies are going to be enacted there before data even leaves the system. They're going to be done consistently throughout the system,” Brown concluded. 📰 Get the full story: https://lnkd.in/guy2N3wz #EnterpriseTechNews #AWSFinServ AWS for Financial Services

So we were talking about this new Vogon data storage using DQLBD. How is it done? How do I store my data on Vogon? To store your data on the Vogon Distributed Quantum Ledger Database (DQLDB), you will need a VogonID, which is a decentralized ID specific to the Vogon system. Here’s a general outline of the steps you might follow, based on the information provided: Obtain a VogonID: Since VogonID is essential for accessing the Vogon DQLDB, you will first need to register and obtain this ID. This process will likely involve verifying your identity and setting up cryptographic keys that will be used for secure access. Access Vogon DQLDB: With your VogonID, you can access the Vogon DQLDB. You will need to use specific tools or interfaces provided by Vogon Cloud, which might include web portals, APIs, or specialized client software. Prepare Your Data: Before uploading your data, ensure it is formatted correctly and complies with any data input standards or protocols Vogon DQLDB requires. This might involve structuring your data into JSON format, as Vogon leverages a deterministic concurrent process for generating JSON-formatted data. Secure Data Transmission: Utilize the quantum cryptography features of Vogon DQLDB, such as quantum key distribution (QKD), to encrypt your data during transmission. This ensures that your data remains secure and private. Store Data: Upload your data to the Vogon DQLDB. The specifics of this process will depend on the interface you are using, but generally, you will be able to execute transactions that record your data onto the ledger. Manage and Access Data: Once your data is stored, you can manage and access it through the Vogon system using your VogonID. The decentralized and secure nature of the DQLDB allows you to maintain control over your data. For detailed instructions and support, it is best to consult the official documentation provided by Vogon Cloud or contact their support services directly. They can provide you with specific guidance tailored to your needs and the particularities of their system. Https://www.spectralcapital.com $FCCN

The end of Enterprise Vault?!?... after working with EV for over 20 years, all the way back to the KVS days, it's clear the product is more than just dated. Veritas/DataCo/Arctera has a well defined agenda to eliminate these burdonsom deployments and promote SaaS moving forward at a very high cost to customers. For any organization (under maintenance or not) It's definitely time to consider modernizing these legacy archive deployments that hold so much ROT (redundant, obsolete and trivial data) + associated risk! If you're looking to instil good data hygiene while executing a well orchestrated transformation from Legacy EV then Cloudficient has you covered! #Cloudficient #Expireon #RightSizedeDiscovery #TargetedIndexing #DataAutonomy #M365 #LeftSideEDRM

WWT has identified six common challenges and misconceptions that typically arise when helping organizations implement a software-defined data center (#SDDC). https://lnkd.in/gGfHg-XT

WWT has identified six common challenges and misconceptions that typically arise when helping organizations implement a software-defined data center (#SDDC). https://lnkd.in/eZdPCgYx

Understanding EIP-1967: A Key Standard for Proxy Storage in Ethereum 💥 In Ethereum, upgradeable contracts are a crucial feature, allowing smart contracts to evolve without losing data. EIP-1967 addresses a key challenge in this process by standardizing how proxy contracts store the addresses of the logic contract (implementation) and the admin (who controls upgrades). Let’s take a closer look at why EIP-1967 matters. 🚀 What is EIP-1967? EIP-1967 was introduced to solve a problem that existed in upgradeable contracts: there was no unified way of storing critical proxy data, such as the implementation address. Previously, different proxy designs, like OpenZeppelin’s or the Ethereum Foundation’s, stored these addresses in unique ways, creating inconsistency and the risk of storage collisions. 📦 The Problem Before EIP-1967 Before EIP-1967, developers stored proxy addresses in arbitrary storage slots, which could conflict with user-defined storage variables in the implementation contract. This led to issues like: Storage Overlaps: If the proxy and logic contracts unintentionally used the same storage slots, data could be overwritten. Difficult Audits: Non-standardized storage made it harder for auditors to track the location of the implementation address, making contracts more error-prone and insecure. 🛠 EIP-1967’s Solution EIP-1967 introduces pre-defined storage slots for the implementation and admin addresses, avoiding any overlaps. It does so by using the hash of a unique string and subtracting 1 to create a secure and predictable location for these addresses. Implementation Slot: keccak256("eip1967.proxy.implementation") - 1 Admin Slot: keccak256("eip1967.proxy.admin") - 1 These slots ensure that implementation and admin addresses are isolated from user storage, making the process safer and more predictable. 🔑 Benefits of EIP-1967 EIP-1967 standardizes proxy storage, delivering key benefits: Compatibility: Contracts that follow EIP-1967 can more easily integrate with various upgradeable proxy patterns. Storage Safety: The risk of accidentally overwriting important data in the proxy or implementation contract is minimized. Auditing Simplicity: Auditors know exactly where to look for proxy addresses, making security checks faster and more reliable. ⚡ Conclusion EIP-1967 is a small but impactful improvement that enhances the security and reliability of upgradeable smart contracts in Ethereum. By standardizing how proxy addresses are stored, it reduces the risk of storage conflicts, simplifies audits, and ensures better compatibility across projects. Have you used EIP-1967 in your upgradeable contracts? Share your thoughts and experiences in the comments! #Ethereum #EIP1967 #SmartContracts #Blockchain #Solidity #Web3

consistency is negotiable

🖇️𝐋𝐞𝐯𝐞𝐥𝐬 𝐨𝐟 𝐂𝐨𝐧𝐬𝐢𝐬𝐭𝐞𝐧𝐜𝐲 𝐢𝐧 𝐃𝐢𝐬𝐭𝐫𝐢𝐛𝐮𝐭𝐞𝐝 𝐒𝐲𝐬𝐭𝐞𝐦𝐬 - 𝐋𝐢𝐧𝐞𝐚𝐫𝐢𝐳𝐚𝐛𝐥𝐞, 𝐂𝐚𝐮𝐬𝐚𝐥, 𝐄𝐯𝐞𝐧𝐭𝐮𝐚𝐥 𝐚𝐧𝐝 𝐦𝐨𝐫𝐞..🔗 𝘊𝘰𝘯𝘴𝘪𝘴𝘵𝘦𝘯𝘤𝘺 𝘪𝘯 𝘥𝘪𝘴𝘵𝘳𝘪𝘣𝘶𝘵𝘦𝘥 𝘴𝘺𝘴𝘵𝘦𝘮𝘴 𝘦𝘯𝘴𝘶𝘳𝘦𝘴 ✅ 𝐔𝐧𝐢𝐟𝐨𝐫𝐦 𝐃𝐚𝐭𝐚 𝐕𝐢𝐞𝐰: All users see the same data, regardless of which server or node they access ✅ 𝐀𝐜𝐜𝐮𝐫𝐚𝐭𝐞 𝐔𝐩𝐝𝐚𝐭𝐞𝐬: Changes, such as updates or writes, are reflected reliably across the entire system ✅ 𝐓𝐫𝐮𝐬𝐭: Critical for systems with multiple data copies (e.g., databases or cloud services) For example, ➡️ in 𝐛𝐚𝐧𝐤𝐢𝐧𝐠, strict consistency ensures a user’s balance is updated immediately across all nodes after a transaction, as even a 𝒎𝒊𝒏𝒐𝒓 𝒊𝒏𝒄𝒐𝒏𝒔𝒊𝒔𝒕𝒆𝒏𝒄𝒚 𝒄𝒂𝒏 𝒍𝒆𝒂𝒅 𝒕𝒐 𝒇𝒊𝒏𝒂𝒏𝒄𝒊𝒂𝒍 𝒅𝒊𝒔𝒄𝒓𝒆𝒑𝒂𝒏𝒄𝒊𝒆𝒔 𝒐𝒓 𝒍𝒐𝒔𝒔 𝒐𝒇 𝒕𝒓𝒖𝒔𝒕 ➡️In contrast, 𝐬𝐨𝐜𝐢𝐚𝐥 𝐦𝐞𝐝𝐢𝐚 𝐩𝐥𝐚𝐭𝐟𝐨𝐫𝐦𝐬 can tolerate slight delays in updates, such as a like or comment taking a few seconds to appear across devices, 𝒑𝒓𝒊𝒐𝒓𝒊𝒕𝒊𝒛𝒊𝒏𝒈 𝒔𝒑𝒆𝒆𝒅 𝒂𝒏𝒅 𝒂𝒗𝒂𝒊𝒍𝒂𝒃𝒊𝒍𝒊𝒕𝒚 𝒐𝒗𝒆𝒓 𝒊𝒎𝒎𝒆𝒅𝒊𝒂𝒕𝒆 𝒄𝒐𝒏𝒔𝒊𝒔𝒕𝒆𝒏𝒄𝒚. However, 𝒂𝒄𝒉𝒊𝒆𝒗𝒊𝒏𝒈 𝒄𝒐𝒏𝒔𝒊𝒔𝒕𝒆𝒏𝒄𝒚 𝒐𝒇𝒕𝒆𝒏 𝒄𝒐𝒎𝒆𝒔 𝒘𝒊𝒕𝒉 𝒕𝒓𝒂𝒅𝒆-𝒐𝒇𝒇𝒔, as ensuring it can impact system speed, availability, or fault tolerance, depending on the design choices. Different 𝐥𝐞𝐯𝐞𝐥𝐬 𝐨𝐟 𝐜𝐨𝐧𝐬𝐢𝐬𝐭𝐞𝐧𝐜𝐲 (𝐞.𝐠., 𝐬𝐭𝐫𝐢𝐜𝐭, 𝐜𝐚𝐮𝐬𝐚𝐥, 𝐞𝐯𝐞𝐧𝐭𝐮𝐚𝐥) are used based on the needs of the application. This wonderful post by Raul Junco demystifies the different levels of consistency and the tradeoffs they involve along with nice and easy to understand visuals. #Engineering #APIs #EngineeringCommunity #Upskilling #SystemDesign #SoftwareArchitecture #Microservices #TechCommunity #SoftwareEngineering #Programming #CollaborativeLearning

"Slow and secure" used to be the data mantra. The Futurex integration with MongoDB is flipping the script. Their queryable encryption allows: • Equality and range queries on encrypted data • Processing queries server-side • Maintaining index efficiency This solves a major pain point for enterprises dealing with sensitive data. It enables: 1. Banks to protect financial records 2. Healthcare providers to secure patient data 3. Retailers to safeguard customer information All while maintaining the ability to analyze and use that data effectively. Download the integration guide for MongoDB and Futurex Key Management solutions. https://hubs.la/Q02Xbkqf0 #DataProtoction #MongoDB #Futurex #SecurityToTrust #FreedomToDo

🚨 Enterprise Vault Licensing Changes: 3x cost increase? 🤔 Recently, some Enterprise Vault (EV) customers have received emails from Veritas about significant changes to their licensing model. If you’re an #enterprisevault customer, this news might have caught you off guard. Here’s a closer look at what this means and why it’s a cause for concern. 🔍 What’s Happening? Veritas has announced that starting with the March 2025 version, they will begin enforcing new EV usage policies. One of the most notable changes is their licensing model, which now considers both active and legacy users for licensing. Active users are defined as those creating new data or accessing archived data, while legacy users are those who have left the organization but whose data still exists within EV. 🔒 Impact on Licensing Costs This change in policy is not just a minor adjustment—it has significant financial implications. For many customers, this means a substantial increase in licensing and maintenance costs, estimated to be 2.5 to 3 times higher than before, with no additional benefits or features to justify the price hike. Essentially, it appears that Veritas/DataCo is squeezing the last bit of money out of their remaining customers. 💡 The EWS Challenge: Adding to the complexity, Microsoft has announced that it will be abandoning Exchange Web Services (EWS) in Exchange Online (EXO) by 2026. This move means that migrating legacy email data from Enterprise Vault to EXO will become impossible or prohibitively expensive. Microsoft may offer a premium Graph API replacement, but this will likely come at a significant cost, further complicating data management strategies for EV customers. 🤔 Is It Time to Finally Get Out of EV? With Veritas's new licensing policies driving up costs and Microsoft's plans to phase out EWS making data migration more difficult and expensive, now is the time for EV customers to reevaluate their data management solutions. Is it worth staying with Enterprise Vault under these new conditions, or is it time to consider alternative solutions that offer better value and future-proof capabilities? At Cloudficient, we believe in transparent, customer-first approaches to data management and governance. If you’re feeling the pinch from these changes, it might be time to explore alternative solutions that provide real value without breaking the bank. 📣 Join the Conversation Have you received a similar email from Veritas? How are you planning to manage these changes? Share your thoughts and strategies in the comments below. Together, we can navigate these challenges and find better ways to manage our data efficiently and cost-effectively. #enterprisesoftware #legaltech #archiving #compliance #informationgovernance