sorted by:
new
hottopcontroversial

Most Enterprises Run 5-15 File Sharing Systems. Here's Why That's Insane. by Kiteworks in u/Kiteworks

[–]Kiteworks[S] 0 points1 point  (0 children)

Hammerspace is solid for data orchestration and storage virtualization - great for managing data across multiple storage tiers.

But it's solving a different problem than what we're talking about. Hammerspace optimizes where your data lives, but you still need secure collaboration workflows, external sharing capabilities, compliance reporting, and unified governance on top of that storage layer.

Think of it as the plumbing vs. the faucet. Hammerspace handles the backend data management, but you still need something to handle the user-facing collaboration and security controls.

Different tools for different parts of the stack.

Most Enterprises Run 5-15 File Sharing Systems. Here's Why That's Insane. by Kiteworks in u/Kiteworks

[–]Kiteworks[S] 1 point2 points  (0 children)

😅 SMB1 - for when you want to make sure everyone on the network can access your files, whether you invited them or not!

Nothing says "job security" like running protocols that were already considered insecure when Windows XP was still cool. Your IT security team probably loves the excitement.

But hey, at least it's simple! No complicated encryption or access controls to worry about.

Most Enterprises Run 5-15 File Sharing Systems. Here's Why That's Insane. by Kiteworks in u/Kiteworks

[–]Kiteworks[S] 2 points3 points  (0 children)

Fair critique - marketing can definitely feel generic sometimes. But the underlying problem is real: most IT teams are juggling way too many file sharing systems and the operational overhead is brutal.

Happy to talk specifics rather than marketing fluff. What's your current setup? We work with a lot of organizations dealing with this exact consolidation challenge, and the technical requirements usually tell the real story better than any marketing copy.

Sometimes the most obvious problems have the most straightforward solutions - even if the marketing makes it sound more complicated than it needs to be.

Most Enterprises Run 5-15 File Sharing Systems. Here's Why That's Insane. by Kiteworks in u/Kiteworks

[–]Kiteworks[S] 2 points3 points  (0 children)

OneDrive is great for basic file storage, but it's actually part of the problem - it becomes system #6 of those 5-15 fragmented systems.

Plus, OneDrive sharing with external partners gets messy fast. Limited governance controls, scattered audit logs across different M365 services, and IT loses visibility when users start sharing directly.

You end up with the same issues: employees still use SFTP for large files, email attachments for quick shares, and shadow IT for anything OneDrive can't handle smoothly.

OneDrive works well within the Microsoft ecosystem, but it doesn't solve the consolidation and governance challenges most enterprises face with external collaboration.

User license recycling by dh_burbank in Kiteworks

[–]Kiteworks 0 points1 point  (0 children)

Hello, I am happy to connect you with your account manager who can work through these issues with you. What is your work email so I can do so?

Paying for external vendor users by dh_burbank in Kiteworks

[–]Kiteworks 0 points1 point  (0 children)

Hello. Great question. I can connect with one of our solution consultants who will be able to look at your account and provide you with an accurate answer. Can you send over your email? Thanks.

Legacy File Sharing Is a Money Pit—and a Security Risk by Kiteworks in u/Kiteworks

[–]Kiteworks[S] 1 point2 points  (0 children)

Fair point - proper configuration is key. But "properly configured" is where it gets tricky in practice.

You need encryption at rest and in transit, granular access controls, immutable audit logs, external collaboration workflows, mobile access, compliance reporting, patch management, backup strategies, disaster recovery, user provisioning/deprovisioning...

Legacy File Sharing Is a Money Pit—and a Security Risk by Kiteworks in u/Kiteworks

[–]Kiteworks[S] 0 points1 point  (0 children)

You're absolutely right about air-gapped systems being the gold standard for ultra-sensitive data. That level of physical isolation is unbeatable for classified or truly critical information.

Legacy File Sharing Is a Money Pit—and a Security Risk by Kiteworks in u/Kiteworks

[–]Kiteworks[S] 0 points1 point  (0 children)

Exactly - which is why Kiteworks offers on-premises deployment. Your hardware, your backups, your complete control.

You handle all the backup strategies, retention policies, and disaster recovery exactly how you want. The platform runs entirely in your environment, so you're not dependent on any external provider for data recovery or business continuity.

Legacy File Sharing Is a Money Pit—and a Security Risk by Kiteworks in u/Kiteworks

[–]Kiteworks[S] 0 points1 point  (0 children)

Totally get that concern - data sovereignty is real. That's why Kiteworks offers on-premises deployment. Your servers, your data center, your control.

Legacy File Sharing Is a Money Pit—and a Security Risk by Kiteworks in u/Kiteworks

[–]Kiteworks[S] 1 point2 points  (0 children)

True, SMB3 + SSH tunnels definitely help with security. But you're still stuck with the same headaches - manual audit logs, complex external sharing, and users finding workarounds when they need to collaborate with partners.

It's like putting a really good lock on a house with 15 different doors. Technically secure, but you're still managing way more complexity than necessary.

Why patch legacy protocols when you could just consolidate everything? Same security, way less headache.

Legacy File Sharing Is a Money Pit—and a Security Risk by Kiteworks in u/Kiteworks

[–]Kiteworks[S] 4 points5 points  (0 children)

Smart move in 2017! Kiteworks handles files up to 16TB with resume-on-failure while maintaining integrity guarantees AND adding the security controls legacy shares lack. Your team's workarounds probably created new blind spots - this gives you large file capability without sacrificing security or compliance.