Now hopefully you've had a chance to play at home and try some of those
commands already and
take a look inside of our NX API sandbox. And if you have had a chance to play
at home, you'll
notice that one of those three areas did not come up inside of here and I want
to explain why
I have momentarily. But if you're like me and you have a little rest on you as
far as like your
Cisco command lines go sometimes, you can always click on your command
reference and pop open to
see what's actually going on here. And you can see I did that for SNMP. So we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
see what's actually going on here. And you can see I did that for SNMP. So we
're going to take a
look at our API here real quick and we're just going to do a very simple show
SNMP. And we're going
to actually send the request and go down here and take a look at our response.
Now this allows us
to be able to go through and take a look at our SNMP configuration and also see
where we can make
changes inside a Nest Comp or Net Comp or Rest Comp as far as how we want to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
changes inside a Nest Comp or Net Comp or Rest Comp as far as how we want to
send it to our mass
devices across the infrastructure if we wanted to do so or we could just
configure them individually.
And it's mostly to be able to go through and configure devices to on an
individual level and to
basically send a basic configuration to get things ready for our actual network
. Because if you
take a look at the actual response that we get from show SNMP, you can see that
we have version
of TCP authentication status and protocol status. Now we do have our same WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of TCP authentication status and protocol status. Now we do have our same
community names for
for being able to read or write and whatnot to have access to be able to
monitor what's actually
going on. But you can see that we also have encryption like right here it says
AES 128 and we can
actually go through and make sure that our SNMP configuration is secure on that
IP level. The next
one that we went into was NTP and this was an also show NTP and I wanted to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
one that we went into was NTP and this was an also show NTP and I wanted to
show you the
well I'm going to show you live that I messed that up and I'm going to do a
search for NTP because I know
that's command in here and I'm going to go down to it and that's why this
command reference is
really good. But the reason I wanted to show this one is because we are going
to show our NTP
authentication status and while we're doing that I'm going to explain that NTP
allows us to be able
to sync up our different devices based on time sync. We want to have one or WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to sync up our different devices based on time sync. We want to have one or
maybe a one primary
and one backup timing source to make sure that all of our devices on the
network whether they be
on a physical or a cloud environment are all time sync. There are different
resources and
services out there that require us to be within time. For instance, Microsoft
Server requires servers
to be within a certain time skew to be able to do authentication inside of
Active Directory. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Active Directory.
Comp-seg devices or cryptographic devices on the DOD side require that time be
set on those as
well because if a packet is sent at let's say 12 o'clock on the nose and it
arrives at
at 1 o'clock but that time skew is off by an hour. Regardless of whether the
cryptic app graphic
keys are correct it will not accept the packet because the time has not been
synced up between the two
devices. And by going in and doing a show NTP authentication status inside of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
devices. And by going in and doing a show NTP authentication status inside of
our API sandbox here
we can also see the NTP right now the authentication is disabled. Typically you
can set up NTP just
to point to a server and say use that for actual time sync. But if we wanted to
be a little bit more
secure we have a bunch of NTP reference commands to be able to go through and
configure not just show
but also to configure through NetComper ResCompt to go through and set up NTP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
but also to configure through NetComper ResCompt to go through and set up NTP
on our networking devices
or Cisco related devices as well to make sure that we are set up to be able to
have not only time sync
between all the devices but it's authenticated making it just that much more
secure and making sure
that not everybody can get into our NTP server to send false timing information
over the network.
Now the last one that I gave you that you weren't able to find in here and I'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now the last one that I gave you that you weren't able to find in here and I'll
do a search for
RIPWIC is SysLog. That allows us to be able to send logs from the devices that
encrypted but we don't
want people sneaking in to be able to see the logs being sent for actual
infrastructure in case that
we have a let's say firewall that's gone and fail open and we can't get any
more response from it.
We've got it set fail open just in case that we don't want to toss our own WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We've got it set fail open just in case that we don't want to toss our own
network so the firewall
itself does not work but it's still passing traffic and SysLogs might lead a
baddie out there on the
internet to be able to discover that it could fail open instead of going into
failed closed.
Now the preferred security method is failed closed. I'm just giving you a very
quick scenario to why
SysLog information might benefit a baddie out there and we want to make sure
that SysLog
information is being taken care of from point A to point B within our local WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
information is being taken care of from point A to point B within our local
environment and make sure
that the logs are not being read by just anybody out there. Configuration and
maintenance definitely
gets a lot more intensive when we're swapping over to that infrastructure as a
service. That's why we
always have to keep in mind that logging and making sure that we're keeping
track of everything as
at the utmost of our security concerns. And we've seen the difference between
infrastructure,
platform and software as a service going through the different modeling methods WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
platform and software as a service going through the different modeling methods
and comparing what
we're allowed to do and what different resources that are available to us.
Whether it be something as
simple as going through an actual browser to access a service or making sure
that we can implement
inside of our own environment and expand as needed. I hope this has been a form
of
for you and I'd like to thank you for viewing.