Git ZeroTrust is an operational framework that takes DevOps best practices used for application development such as version control, collaboration, compliance, and CI/CD, and applies them to ZeroTrust configuration and operations enabling an approach formally described as ZeroTrust as Code (ZTaC).
A Technical and Cultural Focus on Teamwork and the Mission to Deliver Software Securely.
- Define Success: Set Overall Mission and Iterative Goals
- Identify Your Path: Build, Implement, and Improve Living Processes with Purpose
- Execute as a Team: Trust, Communicate, and Cooperate
- Transform and Innovate: Experiment, Measure, Analyze, Decide, Act
A trust mindset where all activity is provided the least amount of access, and all connectivity is authenticated and continuously verified to be the expected user.
And, one of the things I've always found is that you've gotto start with the customer experience and work backwards for the technology. You can't start with the technology and try to figure out where you're going to try to sell it.
- Steve Jobs
YouTube Video Link - https://ztac.network/dx
- Establish a corporate identity
- Enforce MFA for all applications
- Implement MDM/UEM to control corporate devices
- Implement endpoint protection
- Inventory all corporate devices, APIs and services
- Block DNS requests to known threats
- Block threats behind SSL/TLS
- Segment user network access
- Use Internet backbones for branch to branch connectivity
- Close all inbound ports open to the Internet for application delivery
- Monitor inbound emails and filter out phishing attempts
- Inventory all corporate applications
- Zero Trust policy enforcement for Applications
- Publicly addressable
- Privately addressable
- SaaS applications
- Non-browser apps (SSH, RDP, SMB, thick clients)
- Protect applications from Layer 7 attacks (DDoS, injection, bots, etc)
- Enforce HTTPS and DNSsec
- Establish a process to log and review traffic on sensitive applications
- Define what data is sensitive and where it exists
- Stop sensitive data from leaving your applications (e.g. PII, CCNs, SSNs, etc)
- Identify misconfigurations and publicly shared data in SaaS tools
- Establish a SOC for log review, policy updates and mitigation
- Stay up to date on known threat actors
- Employ a DevOps approach to ensure policy enforcement for all new resources
- Implement auto-scaling for on-ramp resources
Collaborative automation is simply teams of engineers and administrators working together, towards a common goal, utilizing automation tooling to make their jobs easier, more efficient, and stress free. A secondary DevOps practice configuration management is important to GitZT, and has undergone a fundamental shift over the last few years as social coding via sites like GitHub.com have become increasingly popular. Security and IAM teams will be able to share their Zero Trust modeled environments and configurations as software projects with other enterprise team members, solicit feedback, find bugs, and squash those bugs all through a holistic development and delivery platform.
Learning and understanding how to manage your network infrastructure as a software project is incredibly valuable. Software development has reached a level of maturity allowing its techniques to be utilized in fields such as network engineering. A GitZT workflow can be managed via Agile methodologies such as Scrum and Kanban. This allows network engineers to coordinate and manage their infrastructures with agility and achieve project velocity. Social coding techniques such as peer review increase the quality of the network designs and configuration. Automated tests can be run against the GitZT configurations, finding defects and alerting engineers to bugs found. As GitZT software development maturity increases, there will be fewer bugs and errors, but most importantly project velocity will increase and the network and operations environment will keep pace with the velocity of the ever-increasing software projects they are meant to support.
The agile scrum methodology is a project management system that relies on incremental development. Each iteration consists of two to four-week sprints, where the goal of each sprint is to build the most important features first and come out with a potentially deliverable product.A Scrum moves forward as a unit.
The scrim methodology is named after the line of scrimmage in Football and refers to the whole team moving the line of scrimmage forward every play. Plays are tasks that are performed and have a corresponding yardage associated with completing them. Teams try to earn as many yards as possible each play, and try to score touchdowns for every 100 yards gained. The number of touchdowns scored for each “game” is recorded and can be compared to other teams inside or outside the organization. Scrim uses Football style playbooks and symbols during pre-play huddles to increase the operational awareness of the Development and Operations teams. This provides a visual situational awareness of how the entire team is tasked and what the team is trying to accomplish with each play. This increased visibility results in team members learning what others on the team are struggling with and increases empathy and trust.
As Pittsburgh Steeler hall of famer Iron Mike Webster said at his hall of fame acceptance speech.
Do not be afraid to fail. You're going to fail, believe me. No one's keeping score. All we have to do is finish the game. Then we'll all be winners.
- Repeatability – The very act of modeling your infrastructure in code provides repeatability. Every configuration element is captured in the code and will enforce that defined configuration each and every time it is run. IaC provides confidence that the infrastructure is configured and operating in the way it is supposed to be.
- Automation – The very act of abstracting out infrastructures brings us the benefits of automation.
- Agility – Utilizing collaborative automation techniques like configuration management provide a confidence in the various versions of the code base. This allows an engineer or administrator to roll forward or backward if a problem were encountered. Logs of who did what when are available and can be analyzed to determine who or what caused the problem. This minimizes the average time to fix problems and encourages root cause analysis.
- Scalability – Repeatability plus automation makes scalability much easier, especially when combined with the rapid hardware provisioning that the cloud provides.
- Reassurance – The fact that the architecture, design, and implementation of our infrastructure is modeled in code means we that we can automatically have documentation. Any programmer can look at the source code and see at a glance how the systems work. This is a welcome change from the common scenario in which only a s single sysadmin or architect holds the understanding of how the system hangs together. That is risky- this person is now able to hold the organization ransom, and should they leave or become ill, the company is endangered.
- Disaster Recovery – In the event of a catastrophic event that wipes out the production systems, if your entire infrastructure has been broken down into modular components and described as code, recovery is as simple as provisioning new compute power, restoring from backup, and deploying the infrastructure and application code. What may have been a business ending event in the old paradigm of custom-built, partially automated infrastructure becomes a manageable few hour outage, potentially delivering competitive value over those organizations suffering from the same external influences, but without the power and flexibility brought about by infrastructure as code.
Now is the time to get involved and learn GitZT. Feel free to star this project or feel free to schedule a meeting with Thomas via his calendly - https://calendly.com/mcgonagle