Alright thanks for joining us for this demonstration of the software-defined
perimeter from SafeConnect SDP I'm going to walk you through at a high level how you
would get started I'm going to use the cloud gateway in this example as it's the easiest
approach to get oriented we do have the private gateway as we describe it also that is typically
more for protecting on-premise resources and the vast majority of our customers
are currently using that gateway so to get started you can go to STP impulse.com
as you know OPSWAT acquired impulse recently and the SDP domain has not yet been
updated ok I'm going to click on create an account I'm going to provide my account name
for now I'm just going to use something as a throwaway here I'm going to give my
email address which is also going to just be a throwaway obviously I need to enter a password
skip that and I'm gonna let them know I'm not a robot and we're ready to register
and I'm going to get an email sent to me for confirmation so I'm going to be looking for
that off screen here and as soon as it arrives I'm going to click through and I'm going to then
I'm going to then start to finish the rest of the registration process once I do get
registered the you see this URL here is going to be my sort of my account or my tenancy and
I can get redirected back to that at any time it going to SDP.impulse.com or going back to
the email I have the email here I'm going to click through and open that and bring
that over on to the screen here for us to see the rest of the process so you can see
that the email that I'd click through on for confirmation has brought me back to
the page where I just need to enter my password that I used when registering
in okay so now once I'm signed in it's a bit of a wizard here that walks you through the process of
setting up SDP there is a deployment guide here that kind of also walks you through exactly what
we're going through here today but again we'll take you through those steps that are involved
the private gateway and so we encourage you to once you're done watching this video continue
into that document from a highest level software if I'm perimeter is about protecting applications
so in terms of configuration the first thing is to tell the software-defined perimeter which
applications to protect next there's users involved you know which users are going to
be permitted to access those applications and the policies are what help govern which users
can access the applications and ultimately we do also need to download the SDP client as that is
used to access those applications well we'll do that during the process of this demo so you can
see the whole picture here so next I'm going to go to the applications when you do create your
account there is an example application that's primed in as a means to help easily test if we
do try to go access this application at this time we'll find out that we won't have access it's
going to timeout because the software-defined perimeter is doing its job there's the cloud
gateway in this case that's going to prevent access until we have the client installed and
we're fully vetted and authenticated such that we can be trusted to access that application
so returning back to the example application definition I'll open this quickly and show
you what it takes to define an application on the box here we offer web applications for door
other other can be a resource or an application so for example you could protect a subnet or you
know a legacy Windows file share obviously you know here you see the SSH and RDP are suggested
so there's a range of capabilities here with a software-defined perimeter here on a web
application we're providing the DNS that you know that the fully qualified URL here to the resource
it could be an IP to but typically for security reasons you'll want to put in a DNS name there
with the URL and you can then specify ports that are going to be protected and I should
mention that if you take the other route and you you're protecting a legacy app you can not
only do multiple ports but you can do a range of IP addresses in a cider notation there is
the option to turn on the ICMP echo and permit pinging across here for diagnostic purposes you
can see that it's off by default and then we provide an image that's going to help the user
identify this application in their client little palette of applications that they see so that's
what's involved in creating an application within the software-defined perimeter next we'll shift
our focus to the users so you can either define a connection to a sam'l IDP identity provider
so you know examples here in this drop-down we have a guided sort of wizard that walks
through configuring the connection to the IDP so these software-defined perimeter is acting
as a service provider for sam'l to allow users to get authenticated and to learn which groups
they should be authorized into so we'll back out of that for now can also define local users within
the software-defined perimeter account here's the account that I created by registering you
see that was automatically created and said as an administrator we could add additional users
here and you know so you have that option either to go through sam'l and leverage
your organization's identity access management system or create them within the system here so
I'm going to go past users now to the policies and as mentioned these policies are going to be
what controls whether a particular user or sets of users are able to access the applications we
define we see that we've got a default policy here as a result so just what the does to help
you get bootstrapped the example application has my user that I registered within it to facilitate
me accessing it and experience in this but had we created other users or if we had gone into sam'l
and configured things this is where we would allow those single users or groups of users to
access that application okay and that's so that's pretty much the high level configuration that the
administrator would do the next step would be to get set up to access to provide access to
end users so here on this page we kind of repeat a little bit of what we've already done you know
we've already tried to access that example web application and that's what this link is for so
you've already seen that you know when we try to access it it just times out so that served
its purpose but you know the next step here would be to download the client in this case I'm on a
Windows machine so it offers me the Windows client if I was on a Mac it would offer to take me to the
Mac App Store we also have iOS and Android apps so now I'll click download on this let it come down
brings up the installer when I click through it's pretty straightforward installation I need
to change this account I've used this previously so it's got a different accounting in here and
I need to enter the account name I gave when I signed up and to just double check on that
if I come back up here I'll see that because sometimes there's confusion with customers
I'll enter an email address here rather than the name they gave for the account when they
signed up so it is just that same value that I gave when I was registering not an email address
so I'm finish the installation
and you can see that it's finished and it started the application you can see
here that it has the account name in the in the title bar here to let me know that
I am on the right account so opslaan SDP one was my account name I'm going to log
in as that user that we created when I started let me see if I still have that
on the clipboard I don't I'm gonna go grab that paste it in here and give my password
and so right it's doing right now is it's creating
a perimeter of one a connection from my endpoint up to the the Gateway using
the fact that we're now seeing this example application means that it has finished that
that authentication and standing up that ability to connect so that application
that we previously tried to connect to here that didn't allow us to access well now load because
we've done what's needed to get authenticated to the Gateway so the client is talked to the
controller asked for the the permission and the client was then given the destination of where
that hidden application lives given the right sort of secret handshake information to build
the packets for a single packet authentication flow over to the Gateway and allow a successful
connection so the fact that we're seeing this page load is an indication that that
has all worked as expected so in summary you've seen the SDP client work able to access what
was otherwise a darkened application that was hidden from us we've walked through the steps
to do the initial configuration which involved in which applications to protect which users
either through sam'l or natively within the SDP account set up the policies installed the client
went through the full the full procedure here to help you understand and and how to protect
an application with a software-defined perimeter so that's that's it in a nutshell so I encourage
you the next steps would be to use that guide that we mentioned in the start state here to
finish deploying presumably an on-premise or self-hosted gateway thanks for your time bye