Secure Immutable Cloud Storage Setup

$25-50 USD / hour

Posted 1 minute ago

•

Ends in 6 days

$25-50 USD / hour

The task is needed to be started urgently and now. I need someone who can set up safe cloud storage in multiple services: google cloud; cloudflare non deletable, proton drive and maybe some more. Need a person who can create corporate account google for me and set it up all files to not be able to delete. And transfer all my files from my google drives to there saving metadata initial. And who can upload materials from flash drives to cloud storage. Also need to set up safe AI which will be working 24/7 and analyzing materials uploaded and it to be protected from MITM attack, prompt injecting. And to be protected from devices which were hacked and under MDM. Cloud files should be safe and non deletable / non changeable.

Project ID: 40805792

About the project

19 proposals

Open for bidding

Remote project

Active 3 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

19 freelancers are bidding on average $31 USD/hour for this job

User Avatar
Flag of UNITED STATES

Hi, I am Elias from the sunny state of Florida. I see you're looking to set up secure cloud storage urgently. It's crucial to ensure that your data is not only stored safely but also remains accessible and scalable. A common issue in systems like this is managing access permissions while ensuring data integrity and availability. The tricky part is usually balancing security with usability, particularly when integrating with existing workflows or third-party services. My approach would involve establishing a robust cloud architecture that prioritizes security and ease of maintenance. I would recommend using industry-standard encryption techniques and implementing strict access controls. This ensures that your data remains protected while being ready for future scaling or integration needs. I have experience setting up similar secure cloud environments, focusing on both Linux-based systems and cloud security measures. A few questions to better understand the scope: Q1 – What specific data types are you planning to store in the cloud? Q2 – Are there any existing systems or workflows that this setup needs to integrate with? Q3 – What are your long-term scaling expectations for this storage solution? Happy to go through the details and suggest the best technical approach. Looking forward to hearing from you.

User Avatar
Flag of INDIA

Hello, Could you share your approximate storage requirements and current Google Drive setup? I’d design a secure, multi-provider cloud storage system using Google Cloud, Cloudflare, and Proton Drive, with a focus on immutable backups and protecting your files. I recommend configuring retention policies, object versioning, access controls, encryption, secure file migration with metadata preservation, and automated backups. For AI, I’d implement a controlled analysis workflow with prompt-injection protection, isolated processing, and secure API communication. I’ll handle the cloud configuration, file migration, flash-drive uploads, security testing, and documentation. Corporate account ownership and recovery will remain under your control. Let's build a reliable, secure, and tamper-resistant cloud storage environment! Best Regards, Priyanka

User Avatar
Flag of PAKISTAN

Hi, I can help set up a secure, immutable cloud storage system across Google Cloud, Cloudflare, Proton Drive, and any suitable backup service. I will configure corporate access, retention or object-lock policies, migration with metadata preserved, and controlled uploads from your flash drives. I will also review the 24/7 analysis setup for MITM attacks, prompt injection, compromised devices, and MDM-related risks. Cloud Computing and Linux experience will support a clean setup, while System Admin and Web Security practices will keep access, logs, keys, and recovery procedures under control. Would you like immutable storage to use strict write-once retention, and how long must files remain permanently protected from deletion or changes? Please start a chat and let’s discuss the urgent setup, current files, and the safest rollout plan.

User Avatar
Flag of TURKEY

Hi there, I can help you set up secure and immutable cloud storage across Google Cloud, Cloudflare, and Proton Drive. Transitioning your files while preserving their metadata will be key, and I can automate the transfer from your existing Google Drives. Additionally, I can configure your corporate Google account with non-deletable settings. I'll also implement continuous AI monitoring to analyze uploaded content while guarding against MITM attacks and ensuring protection against potentially compromised devices. I'm ready to start immediately to meet your urgent needs. Regards, Ali

User Avatar
Flag of NIGERIA

Hi, Migrating active drives into immutable storage while keeping metadata intact fails if native sync tools strip creation timestamps, so I pull via CLI using rclone with flag retention enabled rather than web UI drag-and-drop. I provision corporate Google Workspace accounts, configure Cloudflare object storage with strict WORM locks, and set up local ingestion from your flash drives. I will also deploy your 24/7 AI container with mutual TLS, strict input sanitization filters against prompt injection, and endpoint attestation to block compromised MDM devices. For $33 total, delivery takes 7 days, covering the full workspace setup, metadata-preserving migration, WORM object locking, and the hardened AI analysis pipeline. Shall we start by provisioning the Google Workspace and setting up the initial rclone sync profile?

User Avatar
Flag of MEXICO

Hello! The most important part of this setup is making sure your files remain protected even if an account or connected device is compromised. Simply storing files across multiple cloud services is not enough. I can help assess the architecture and build a secure storage workflow around immutable backups, restricted access, encryption, and audit logging. I would first configure retention or object-lock protections, then plan the migration from your existing Google Drives while preserving available metadata and verifying file integrity. Flash-drive uploads can be included in the same process. For the 24/7 AI component, I would keep it isolated from direct access to original files, use controlled read-only processing, and add safeguards against prompt injection and untrusted inputs. I would also assess device and identity risks before connecting any endpoints. I suggest starting with a security and architecture assessment so we can establish realistic protection guarantees before deployment. Kind regards, Fernando Estimated timeline: 5–10 days for the initial storage setup and migration, depending on data volume, metadata requirements, and cloud account access. The AI service and security hardening may require additional time after the architecture review.

User Avatar
Flag of SERBIA

I can design and implement a secure, multi-provider storage architecture using Google Cloud, Cloudflare, Proton Drive, and any additional services required. The setup can include organization and corporate account configuration, least-privilege IAM, MFA, centralized audit logging, encrypted transfers, retention policies, object versioning, and legally compliant WORM/immutable storage controls. I can migrate existing Google Drive data while preserving metadata where supported, validate file integrity with checksums, and establish a controlled workflow for importing files from removable media. For the 24/7 AI workflow, I can define an isolated processing environment with private networking, encrypted secrets, signed inputs, prompt-injection defenses, content isolation, strict tool permissions, monitoring, and protection against compromised or managed devices. I will also document recovery procedures, retention limitations, access policies, and verification tests so “non-deletable” and “non-changeable” requirements are implemented realistically and auditable across each provider. I can begin urgently with an architecture and risk review, followed by a staged deployment and migration plan.

User Avatar
Flag of SLOVAKIA

I can help, but some goals need reframing to be achievable. "Non-deletable" storage doesn't exist anywhere — what's possible is Google Cloud retention locks/object versioning, Cloudflare R2 with immutability policies, and Proton Drive versioning, all of which prevent accidental deletion but not an admin with full rights. Metadata-preserving transfer (rclone) is doable. For the AI, MITM protection via TLS/pinning and prompt-injection defenses are mitigations, not guarantees, and MDM-compromised devices can't be fully trusted. I won't create a Google corporate account under my identity — I'll guide you through creating it as owner. What's your budget and priority order?

User Avatar
Flag of UNITED KINGDOM

⮜⮞⮜⮞⮜⮞⮜⮞I WILL HELP YOU UNTIL END WITH MY BEST⮜⮞⮜⮞⮜⮞⮜⮞ Thanks for seeing my proposal. I can set this up: Google Workspace corporate account with Cloud Identity, Cloud Storage buckets using Object Retention Lock and Bucket Lock for true WORM immutability, Cloudflare R2 with retention policies and API tokens scoped to write-only so nothing can be deleted, and Proton Drive for encrypted personal-tier storage—plus transfer of your existing Google Drive files with metadata preserved via rclone, and ingestion from flash drives with checksum verification. For the 24/7 AI layer I'd isolate it behind a hardened gateway: TLS pinning and certificate validation against MITM, strict system-prompt isolation and input sanitisation against prompt injection, no direct credentials on MDM-managed or compromised devices (access via short-lived scoped tokens only), and full audit logging. On reply I'll confirm the exact setup sequence and timeline. Questions: 1) Roughly how much data (TB) needs migrating, and do you need version history preserved or just the current files with original timestamps and folder structure? 2) Should the AI layer use a hosted model API (OpenAI/Anthropic) or must it run on your own infrastructure for data-residency reasons?

User Avatar
Flag of PAKISTAN

I understand the critical need for urgent, secure, and immutable cloud storage across multiple platforms. My experience includes architecting and implementing robust data protection strategies for sensitive information, similar to the non-deletable storage requirements you've outlined for Cloudflare. I can ensure your corporate Google account is set up with policies that prevent accidental or malicious deletion, maintaining data integrity. My approach will involve leveraging Google Cloud's Object Versioning and Bucket Lock features to enforce immutability. For Cloudflare, I'll configure Workers and KV storage with appropriate access controls to achieve similar non-deletable properties. Proton Drive will be integrated via its API for automated uploads. File transfer from existing Google Drives will utilize `gsutil` with metadata preservation, and flash drive uploads will be automated through secure scripting and access policies. For the AI component, I'll deploy a containerized model within a VPC, protected by Cloudflare's WAF and DDoS mitigation, to safeguard against MITM attacks and prompt injection. To ensure alignment, could you clarify the specific compliance requirements driving the need for immutability across these services? Additionally, what are your primary concerns regarding the AI's interaction with the stored data beyond the security aspects mentioned? I'm available to discuss these details and outline a precise implementation roadmap.

User Avatar
Flag of THAILAND

I’ve set up Google Cloud archival storage and secure file migrations with retention controls, audit trails, and metadata preservation. For this project, the key is using Google Cloud Storage buckets with Bucket Lock and versioning because true immutability must be enforced by retention policies, not just user permissions. I’ll create and configure the corporate Google environment, migrate files from your existing Drives while preserving timestamps and folder structure where available, and ingest material from flash drives through a verified workflow. I’ll configure least-privilege access, MFA, logging, encryption, and recovery procedures, then verify that retained objects can’t be altered or deleted before their retention period. For the AI workflow, I’ll isolate processing, use signed access paths, and add prompt-injection safeguards. Thanks, Kittipong

User Avatar
Flag of PHILIPPINES

Hello, In my opinion, the problem of this project is that secure, non-deletable cloud storage needs to be implemented across multiple platforms while ensuring data integrity and protection against various threats. I will architect a multi-cloud solution leveraging Google Cloud for corporate account setup, Cloudflare for non-deletable storage, and Proton Drive for additional security. Data will be transferred using automated scripts to preserve metadata, and materials from flash drives will be uploaded using secure APIs. I will implement AI-driven monitoring with strict access controls to prevent MITM attacks and prompt injections, ensuring all files remain immutable and safe. The deliverable will include a fully configured multi-cloud storage environment, with all files transferred, secure AI monitoring in place, and comprehensive documentation. I have successfully deployed similar architectures in the past. I can start immediately. Regards.

User Avatar
Flag of PAKISTAN

Cloud Computing is the core skill I would apply to this urgent storage project, supported by hands-on experience building AI agents, automation systems, and web applications that run reliably in the cloud. I can help structure your Google Cloud environment and connect the required storage and AI components into a controlled corporate setup. My background with AWS, Docker, Python, Node.js, FastAPI, PostgreSQL, OpenAI, Claude, and LangChain is relevant to building a protected 24/7 AI processing service for uploaded materials. I can also develop the supporting automation for transferring files from Google Drive and flash drives while preserving available metadata, with clear ownership, documentation, and controlled access at handover. Security-sensitive requirements such as immutable, non-deletable storage, device trust, MITM protection, and prompt-injection resistance require careful configuration and validation rather than assumptions. I would be glad to take ownership of the cloud and AI implementation and provide a clean, documented setup.

User Avatar
Flag of INDIA

Hello, You're looking to migrate and secure files across multiple cloud platforms, including Google Cloud, Cloudflare, and Proton Drive, while ensuring they're non-deletable and retain metadata. The tricky part here is setting up robust protections against MITM attacks, prompt injection, and compromised devices, especially with the AI component running 24/7. I'd start by creating and configuring the corporate Google account, ensuring files are locked and non-deletable. Next, I'd migrate your existing files while preserving metadata and upload materials from flash drives. For the AI, I'd set up secure endpoints using encryption and access controls to prevent unauthorized tampering. Tools like Cloudflare's Zero Trust or AWS Shield could help mitigate MITM risks. I delivered something similar last month, a document-analysis chatbot with RAG that was secured against prompt injection and unauthorized access. What specific type of AI analysis do you need, text, image, or both?

User Avatar
Flag of UNITED STATES

Hi there, You need an urgent, tamper-resistant cloud storage architecture with non-deletable files, preserved metadata, secure migration from existing drives and removable media, plus a continuously running AI workflow protected against MITM attacks, prompt injection, compromised devices, and unauthorized administration. I have strong hands-on experience with System Admin and Linux environments and have solved similar problems involving immutable backups, access control, secure migrations, and hardened automation. My approach would be to: * Review the existing accounts, storage structure, devices, access policies, and current implementation. * Identify the root cause and determine what can be reused versus what needs to be changed. * Implement a clean, maintainable solution using cloud retention policies, versioning, least-privilege access, encryption, and hardened Linux services. * Test edge cases, reliability, performance, security, and integration behavior. * Deploy or integrate the fix without disrupting the existing system. Object-lock or equivalent retention controls must be configured at the correct organizational level because ordinary permissions alone cannot guarantee non-deletion or immutability. I prefer fixing the actual root cause rather than applying temporary patches, and I will keep the implementation simple, stable, and maintainable. I can start by reviewing the storage accounts, migration sources, device posture, and current setup and proceed with th

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

把喜欢的内容,留在你的新标签页。

打开我的订阅