**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.**

Yes, I am authorized to act on the copyright owner's behalf.

**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**

Yes

**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.**

3751550

**Does your claim involve content on GitHub or npm.js?**

GitHub

**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**

[private] was a contractor of ICEO Lab ltd (a company registered in the [private] under company number [private]

whose registered office is at : [private], hereinafter referred to as the “ICEO”). He was employed as a [private]. Under the cooperation agreement he was obliged to:

a. Create, maintain and develop of infrastructure within GCP and GKE - on high and low-level design for performance at all levels and with security, availability and reliability at the core of it.

b. Take ownership of security best practices across the DevOps lifecycle, ensuring the infrastructure is hardened and secure at every layer, from the first point of contact with the external client to the network and application layer.

c. Implement and maintain security measures such as vulnerability scanning, patch management and security automation tools to detect, mitigate and remediate risks proactively.

d. Ensure continuous compliance with industry standards and regulations, including data protection policies (e.g., DORA, ISO, GDPR, SOC2, etc.), working alongside compliance, technology and security teams to meet audit requirements.

e. Develop and enforce security controls within the CI/CD pipeline, integrating security testing, static/dynamic code analysis and vulnerability scanning into the development process.

f. Design and implement secure network architectures, focusing on secure access, encryption and the segmentation of cloud environments, leveraging tools like VPNs, Firewalls and Cloud-native security services.

g. Monitor, identify and respond to security incidents and alerts, working closely with incident response teams to quickly mitigate threats.

h. Promote a security-first mindset within the organization, educating teams on security best practices and driving improvements in secure coding, deployment and monitoring techniques.

i. Create documentation from the implemented solutions.

j. Research and potential development of new solutions in the market.

k. Build and maintain tools that help in the automation of the software development process in all stages.

As part of the remuneration for the performance of the agreement, [private] agreed to transfer to ICEO all proprietary copyrights (author’s economic rights) to the results of tasks performed by him. Based on aforementioned provision - the copyrights to the works (which were almost identical to the ones in the repository) belong to ICEO.

I act as a [private] who's working in a law-firm which is a contractor of ICEO. We have a relevant power of attorney.

**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**

The original copyrighted work is a proprietary Terraform codebase created exclusively for ICEO, a company operating within the [private] and the [private].

This work was developed in its entirety by an employee in his capacity as a [private] engineer during the course of his employment at ICEO. Accordingly, all intellectual property rights to the code belong solely to ICEO.

The codebase is structured as a monorepository containing a set of custom Terraform modules designed to provision and manage infrastructure on Google Cloud Platform (GCP). It implements industry best practices for security, resilience, and compliance in financial services, and was explicitly tailored to support regulatory obligations, including the Digital Operational Resilience Act (DORA) and related EU financial regulations.

The original work includes the following modules and components:

bastion: secure bastion host setup for controlled administrative access.

cloudsql: deployment and configuration of Cloud SQL instances, including encryption, automated backups, and high availability.

gke: provisioning and securing Google Kubernetes Engine clusters with compliance-focused configurations.

iam: granular identity and access management (IAM) roles and policies, following least-privilege principles.

iap: Identity-Aware Proxy (IAP) integration to secure access to internal applications and resources.

memorystore: managed Redis instances configured for high availability and failover.

svc-projects: service project structure for workload separation and compliance enforcement.

svpc: shared VPC configurations to enforce centralized network security controls.

vpc-sc: VPC Service Controls for enhanced data exfiltration prevention and regulatory compliance.

In addition, the Terraform configurations cover:

IAM and role management: definition of custom roles, binding of service accounts, and strict access policies.

Networking standards: VPCs, subnets, firewall rules, and routing aligned with internal security baselines.

Monitoring and observability: Cloud Logging, Prometheus and alerting policies.

High availability and disaster recovery (HA/DR): multi-region deployments, load balancing, backup strategies, and failover configurations.

This codebase represents significant original authorship in both design and implementation. It is not a generic Terraform setup; it embodies the unique security, compliance, and operational requirements of ICEO as a financial services provider. Its architecture reflects original creative and technical contributions that directly serve our regulated business environment and therefore constitutes protected intellectual property.

The takedown of an almost identical repository was already filed and the repository was succesfully removed (ticket

**If the original work referenced above is available online, please provide a URL.**

**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.**

**Based on the above, I confirm that:**

The entire repository is infringing

**Identify the full repository URL that is infringing:**

https://github.com/cloudon-one/google-landing-zone

**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**

No

**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and <i>must be identified separately</i>. Please read more about <a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">forks.</a> As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:**

**Is the work licensed under an open source license?**

No

**What would be the best solution for the alleged infringement?**

Reported content must be removed

**Do you have the alleged infringer’s contact information? If so, please provide it.**

[private]

[private]

[private]

[private]

**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.**

**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**

**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.**

**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**

**So that we can get back to you, please provide either your telephone number or physical address.**

[private]

**Please type your full name for your signature.**

[private]