Anshuman (Andy) Patel – Enabling the Tactical Edge through DevSecOps in a Box

The ability to have the most recent updated information at the tactical edge where there's no or intermittent network connectivity can save lives or can cause a loss of a battalion. Andy Patel with Jasper Solutions is going to talk to us about enabling the tactical edge, the deficit gaps in a box. That's where they've created a capability to enable operations at the tactical edge and give them the ability to modify any application to fit an environment.

Everyone, Andy Patel from Jasper Solutions, that everybody is doing well, how familiar are you guys with mission requirements and field operations support supporting of our war fighters, sailors, airmen and Marine personnel at the tactical edge of. Takes a slightly different approach, right, than your traditional applications and what you guys do today while working with customers. Today, I'm here to talk about really the tactical edge in a box using desktops and multi cloud capability to support our warfighter needs and disconnected and disjointed.

Here's the agenda for today, primarily talking about her journey through check ups, check ups, pipeline and some of the lessons learned, we'll provide some overview overview as to what we actually do and how we are actually doing. Some of the tactical tactical solutions today. Jasper, our strategy is based on two simple tenets mission impact, where we well, technology from back office function to a core part of our capabilities and operating at mission speed where we can quickly take ideas from lab to create competitive solutions.

What problems are we trying to solve today? So we primarily focus on US public sector, deliver real solutions to our operations team, provide timely security to all of our players, midfield and US government compliance requirements, and enable developers to move fast to deliver code at the tactical edge near zero downtime and enable development first mentality and support multi cloud across the cloud as well as commercial. Our journey to deficit and actionable plan, pipeline focus, software development and deployment, an internal application that utilizes artificial intelligence and machine learning at the edge and security and continuous authority to operate at all times.

Automation is everything. So, as I'm sure all of you guys are familiar infrastructure as a code that primarily plays a key role in developing and deploying a policy as a code is something we have adapted to a jasper where we actually enforce policies and a single policy that actually drives anything from on premise, tactical edge to any cloud in between that supports the overall requirement. Containerisation, Carbonetti, ranchers service, Masche and AMAI are primarily the tools that we utilize for platform deployment and scalability, options and service, reliability and monitoring.

Using GitLab obviously across, regardless of where your application resides from on premise to multi cloud and at tactical edge. So we primarily focus on the problem scenario or problem statement, understanding government and customer requirements is first and foremost designing a specific software using Medlab and identifying infrastructure components that supports multi cloud. And obviously that moves into the development and building unit test.

And then you primarily are focused on deploying Thode to excess production and monitoring the health. Obviously we do work on a lot of scenarios such as low to cross the main solutions and currently supporting high to low down to actually support the code moving from different in various classifications of networks. There are many different ways, obviously, as you guys are familiar primarily to deploy and using containerization approach as well as ranter is the communities.

So we focus on the software development as first and foremost and make the flight, the software flexible and enable that tactical edge even without minimal to no network connectivity. And then focus on the infrastructure as the of. This connected network and sensors application development must support disconnected and minimal network connection connectivity.

This really is primarily the biggest challenge for Tactical Edge today and it has been for some time. Our team primarily is focused on supporting applications that enable artificial intelligence, machine learning code, cyber code, as well as existing applications at Tactical Edge. And more than oftentimes, there is no network connectivity or minimal network connectivity.

So we try to focus on building applications that can actually support disjointed and disconnected networks and still maintain and provide the ability to operate key mission sets, container, alkies, orchestration, infrastructure provision, prisoners, governance and enforcement across any cloud. Obviously, containerization is taking a center stage. Infrastructure Provisionary is primarily supporting anything from on prem to multi cloud done cloud or commercial and government enforcement.

Government enforcement plays a key role in how we actually set up the policies across the entire infrastructure as well as applications. How do we maintain ato across any cloud and to ensure that we provide a continuous ATO to enable government agencies to operate at full speed? The mission?

Some of the lessons learned that we have done the same code everywhere is the principle and fundamental value that our team carries from the very beginning of when we start actually addressing to the customer needs and the requirements. Automation and policy plays a key role to ensure all code and infrastructure components remains identical. What does that really mean?

It's primarily automation and policy that drives pretty much the entire software lifecycle delivery from beginning to the end. Security first mentality. Again, I think I have addressed it that talking about the continuous battle, we primarily use Nyst scale and machine learning processes and overlaid it on top of the giving out pipeline that primarily addresses to the security first mentality where we can do checks and balances across continuous fashion while the code is being developed and the code is being deployed and then built.

Pipeline to fit customer needs to adapt to changes at all times and identify gaps. What we have learned over the years is there are times that certain tools and certain infrastructure components may not support the requirements that our customer needs. So we are constantly adapting and making changes to ensure that the customer comes first and we deliver what what really our customers asking and then test and then build testing its key components to make sure that anything that we actually deploy on the tactical edge, if it's using a tactical feel kit or a flyaway kit, then ensuring that we test fully the connectivity to some of the scenarios that may play out in this connected or this disjointed network.

And how do we support multiple enclaves and provide the security for a network across all of us? OS ilers and it's key components. Thank you very much.

Really appreciate it. Any questions or concerns?