<h3>HE WHO RULES THE OS RULES THE APPLICATIONS</h3>
<p>enSilo was built on the concept that if you take away the ability of bad actors to steal data then you remove the majority of your cyber security risk.</p>
<p>To accomplish this, you must be able to silo that data away from those who want to take it. Data theft prevention has been one of the hardest things to accomplish in the cyber security industry for a great many reasons.</p>
<p>These problems get very complex very quickly. It is very hard to know exactly where that data rests in a complex network. More and more complex security tools have been created to look at attack behavior and analysis.</p>
<p>And worse yet they are false alert factories that crank out more and more time wasters for your security team. Which is to say these tools are neither easy to implement or configure. It takes time you don&rsquo;t really have.</p>
<p>Instead of making things more complex, we make thing simpler by looking at the common denominator: the operating system.</p>
<p>Anything that happens on an endpoint has to work through the OS.</p>
<p>Sounds pretty simple, right? The OS runs everything so by controlling how applications behave, you control what data leaves your network.</p>
<h3>GREAT IDEA. HOW DOES IT ACTUALLY WORK?</h3>
<p>We&rsquo;re glad you asked.</p>
<p>enSilo uses two components to prevent data theft and tampering: The Collector and the Core.</p>
<p><img src="http://cobaweb.co/project/arimtechV2/contents/tinyMCE/4-STEPS.png" alt="" /></p>
<h3>SNAPSHOTS &amp; ALBUMS:</h3>
<p>The way it works is we install a Collector on the endpoint or servers. This is a one-time install. No user pop-ups. Nothing. No minimum criteria. It doesn&rsquo;t matter what you have to include Windows XP and macOS. Of course if you have Windows XP endpoints you already know how bad that is. We don&rsquo;t judge you. We just protect your data.</p>
<p>Basically the Collector is like a camera that sits in the operating system. It starts taking snapshots on any process activity. If there&rsquo;s a new process it takes a snapshot. If a process talks to another process, it takes a snapshot. A process might initiate a thread and we&rsquo;ll get a snapshot.</p>
<p>We make a family album of these snapshots of each process. We know everything about that process from the time it was born. We know everything about every process. We know the family of processes.</p>
<p>When one of these processes requests to connect or modify a file, we know who they are by pulling the family album of that process. When this happens the Collector sends the particular request with its family album to the Core for evaluation.</p>
<p>The Core is the brains of the system. The Core looks at the album in combination with the request and looks at the policies to make sure the request has a squeaky clean family album. If the process&rsquo; family album shows a violation, the policy will block that activity.</p>
<p>When you have something sketchy in that family album, we know. And we block. We block the file modification or connection from establishing.</p>
<h3>WE&rsquo;RE PROUD TO SAY WE HAVE TINY FEET</h3>
<p>Our footprint is negligible. Sure. There&rsquo;s plenty of folks that say that but because we&rsquo;re focused on your business running we designed our product to have zero user impact. Because the Core does all the processing, the collector functions passively. And when we move the family album from the Collector, it's only a few kilobytes. The round trip from Collector to Core for album delivery, processing and return is measured in milliseconds.</p>
<p>Click. Done.</p>
<h3>WHY BLOCK JUST THE CONNECTION ESTABLISHMENT?</h3>
<p>You need to keep the ongoing uptime. You need to get work done. Even in a compromised environment. How crazy is that? Unheard of, yes. But not crazy. We keep the bad stuff from happening, so your business runs. You can run any applications you need to. Because we&rsquo;re in the operating system, we don&rsquo;t care what applications you&rsquo;re running. We don&rsquo;t care what protocols are doing. We don&rsquo;t even care where you are: on premise or in the remote.</p>
<p>Now you can forget tracking network monitoring and traffic activity. If the connection goes through then it is legit. If it was not legit, then you don&rsquo;t have to worry. Easy. We focus on the connection where it really matters.</p>
<h3>AWKWARD FAMILY PHOTOS: WHO&rsquo;S UNCLE JOE?</h3>
<p>Look at it this way. When we pull a family album, we can see the members of the family in photo after photo. If you mysteriously gain a new family member it&rsquo;s pretty obvious.</p>
<p>You now have an Uncle Joe. Kind of creepy right?</p>
<p>What happens if you gain extra children? Adoptions have records but someone just randomly appearing in photos is weird.</p>
<p>Creepy Uncle Joe isn&rsquo;t a family member and he should certainly not be in all your photos. And he should certainly not be trying to connect to all the other families you know.</p>
<p>Sure you can only carry the analogy so far but you get the point: when we have the history of the process from when it was born to connection request, we instantly know when something is squirrely.</p>
<p><a class="btn btn-primary block m-t-xlg">Request for an enSilo Demo</a></p>