WEBVTT

00:00:01.990 --> 00:00:02.940
[Autogenerated] in this demo,

00:00:02.950 --> 00:00:06.160
we're going to configure the notifications because

00:00:06.170 --> 00:00:08.870
open C V is an alerting platform,

00:00:09.480 --> 00:00:12.330
we're going to subscribe to vendors and products,

00:00:13.000 --> 00:00:15.730
we're going to verify the mail server settings,

00:00:15.950 --> 00:00:20.830
which is very important since mill is currently the only way to be alerted.

00:00:21.510 --> 00:00:24.280
And we're going to tag a specific vulnerability.

00:00:25.170 --> 00:00:27.610
Let's open our web browser and go to the open C.

00:00:27.610 --> 00:00:27.950
V.

00:00:27.950 --> 00:00:28.970
web instance.

00:00:30.840 --> 00:00:34.350
We can see that the full page for non logged in users.

00:00:34.780 --> 00:00:37.480
If we click on the link at the top right sign in,

00:00:37.560 --> 00:00:40.280
we can sign in using our admin account.

00:00:40.670 --> 00:00:43.100
These are the credentials that we used in the previous

00:00:43.100 --> 00:00:45.500
demo where we created the admin account.

00:00:46.150 --> 00:00:48.360
Let's film the details and click on sign in.

00:00:49.740 --> 00:00:52.250
If you entered the correct log in credentials,

00:00:52.260 --> 00:00:55.160
you'll be greeted with your dashboard and as you can

00:00:55.160 --> 00:00:57.410
see this dashboard is pretty empty.

00:00:57.520 --> 00:00:58.460
Why?

00:00:58.470 --> 00:01:03.160
Because we haven't subscribed yet to any notifications of any product or vendor.

00:01:04.550 --> 00:01:07.960
Let's now assume we want to receive a notification for

00:01:07.970 --> 00:01:09.910
any vulnerability in the product.

00:01:09.910 --> 00:01:14.620
jQuery If you click on vendors and products at the left hand side,

00:01:14.630 --> 00:01:18.770
we get an overview of all available vendors and products here.

00:01:18.770 --> 00:01:21.260
We can search for vendors or products.

00:01:21.440 --> 00:01:27.150
So let's search for jQuery This searches for jQuery in

00:01:27.150 --> 00:01:29.440
defender as well as product name.

00:01:30.020 --> 00:01:33.630
So now sometimes it's kind of a hit and miss to know exactly what

00:01:33.630 --> 00:01:36.000
kind of fender or product you're looking for.

00:01:36.660 --> 00:01:37.750
If you click on the link,

00:01:38.840 --> 00:01:43.240
you will see all CV entries for that specific vendor or product,

00:01:44.150 --> 00:01:46.110
this looks like the correct vendor.

00:01:46.500 --> 00:01:47.070
Okay,

00:01:47.420 --> 00:01:51.770
now we want to be notified if any new CV will be published for

00:01:51.770 --> 00:01:55.200
this specific vendor we can do that by clicking on the

00:01:55.210 --> 00:01:58.440
subscribe button and that's actually it.

00:01:58.800 --> 00:02:00.160
That's how you get notified.

00:02:00.160 --> 00:02:01.300
When anything changes.

00:02:01.300 --> 00:02:06.300
With regards to this specific vendor you subscribe to changes.

00:02:07.310 --> 00:02:10.400
The next step is configuring when you will receive

00:02:10.410 --> 00:02:13.220
alerts email alerts in our instance,

00:02:13.560 --> 00:02:18.240
you can do this by clicking on the top right on your account name and

00:02:18.240 --> 00:02:25.170
then on account here you see an overview of all your subscriptions and

00:02:25.170 --> 00:02:28.030
we just subscribe to the jQuery vendor.

00:02:28.740 --> 00:02:31.020
If you now click on notifications,

00:02:31.030 --> 00:02:35.930
here's when you can set when you receive an alert as you

00:02:35.930 --> 00:02:38.660
can see you can choose multiple options.

00:02:38.790 --> 00:02:41.680
What you want to make sure is that you don't overflow

00:02:41.680 --> 00:02:43.600
yourself with too much information.

00:02:43.760 --> 00:02:49.270
You want to keep the signal to noise ratio acceptable personally,

00:02:49.280 --> 00:02:54.440
what I recommend doing is receiving a notification when a new CVI entry

00:02:54.440 --> 00:02:59.330
for your product or vendor is generated for if one of your subscriptions

00:02:59.330 --> 00:03:05.880
appears for the first time when it's so called CVS s score changes which

00:03:05.880 --> 00:03:10.150
more or less signifies the impact of vulnerability and when its so

00:03:10.150 --> 00:03:12.600
called C pe list changes.

00:03:13.070 --> 00:03:17.400
Cp e stands for a common platform enumeration and matches a

00:03:17.400 --> 00:03:21.930
vulnerability to a specific vendor and product version,

00:03:23.630 --> 00:03:25.400
let's de select the rest.

00:03:25.910 --> 00:03:26.500
Click on.

00:03:26.500 --> 00:03:31.980
Save changes and now every time that a new vulnerability will be

00:03:31.980 --> 00:03:35.960
found for jQuery we will receive a notification.

00:03:36.730 --> 00:03:41.150
However we haven't tested whether the email settings worked yet.

00:03:41.240 --> 00:03:42.610
How can we do that?

00:03:43.210 --> 00:03:47.110
Well, there's a simple trick to check whether the email settings are correct.

00:03:47.870 --> 00:03:51.650
Click on the account button at the top, right and click on sign out.

00:03:52.710 --> 00:03:56.630
This will bring you to the log in page by default.

00:03:56.700 --> 00:04:01.970
Anyone can register a new membership or in other words an account.

00:04:02.450 --> 00:04:04.250
This of course is insecure.

00:04:04.350 --> 00:04:09.580
I assume that when setting up openCV in a production environment that you place

00:04:09.580 --> 00:04:15.200
it behind a reverse proxy server and also take care of encryption ssL TLS

00:04:15.200 --> 00:04:19.560
traffic that falls outside of the scope of this course.

00:04:20.560 --> 00:04:24.420
Now can we use to register a new membership function in order to

00:04:24.420 --> 00:04:26.620
check whether the mail settings are correct,

00:04:27.460 --> 00:04:30.630
fill in a new name and a valid email address,

00:04:31.290 --> 00:04:35.820
then add a random passwords and if you click on register,

00:04:36.570 --> 00:04:40.380
if you then get an error message like you see here,

00:04:40.470 --> 00:04:46.830
then you know that the email settings are incorrect to validate that.

00:04:46.840 --> 00:04:52.130
Let's go back to the console and type in Docker dash compose logs,

00:04:52.140 --> 00:04:55.420
which will show you the log output of all the services.

00:04:56.270 --> 00:05:00.040
Then we see here a message about incorrect sMTP settings.

00:05:00.390 --> 00:05:03.250
This is how you can troubleshoot issues with email as

00:05:03.250 --> 00:05:05.180
well as configuration settings.

00:05:05.950 --> 00:05:07.640
Let's go back to the weapons or face,

00:05:08.420 --> 00:05:12.610
let's log on using the administrative account that we created previously.

00:05:13.720 --> 00:05:14.980
As soon as you log in.

00:05:14.990 --> 00:05:17.630
You see the dashboard with all updates to the

00:05:17.630 --> 00:05:19.820
vulnerabilities that you're subscribed to.

00:05:20.500 --> 00:05:22.770
Currently this is pretty empty for us.

00:05:23.130 --> 00:05:25.460
So let's say you want to be informed about the

00:05:25.460 --> 00:05:27.930
progress of a specific vulnerability.

00:05:29.160 --> 00:05:31.250
Let's click on the shield at the left hand side.

00:05:31.260 --> 00:05:32.310
Vulnerabilities.

00:05:33.130 --> 00:05:35.940
And search for an open ssl vulnerability.

00:05:37.780 --> 00:05:42.520
Let's now select the second vulnerability to 022-3602.

00:05:42.730 --> 00:05:43.840
And let's click on it.

00:05:44.540 --> 00:05:46.080
As of recording of this course,

00:05:46.090 --> 00:05:52.080
this is a relatively new vulnerability and as a system administrator,

00:05:52.090 --> 00:05:55.710
I want to be informed when this vulnerability changes

00:05:55.720 --> 00:05:58.220
anything with regard to this vulnerability.

00:05:58.230 --> 00:06:02.570
What you can do for that is to tag a specific vulnerability.

00:06:03.710 --> 00:06:08.050
Let's go to the right hand side of the screen and click on tags here.

00:06:08.050 --> 00:06:11.520
You can attach a specific tag to a vulnerability.

00:06:12.670 --> 00:06:15.150
We don't have defined any tags yet.

00:06:15.580 --> 00:06:20.090
Let's click on manager tags here.

00:06:20.090 --> 00:06:21.900
We can create a new tag.

00:06:23.500 --> 00:06:28.490
Let's go with production and with the description running on live environment.

00:06:30.900 --> 00:06:35.540
Let's click on create and now we created a tag called production.

00:06:36.900 --> 00:06:42.000
If you now go back to our search results and refresh the page.

00:06:43.030 --> 00:06:45.350
If you now click on text at the right hand side.

00:06:46.230 --> 00:06:49.980
Now we can add the production tag to this specific vulnerability.

00:06:50.470 --> 00:06:55.900
Let's click on production, then let's click on update associated tags.

00:06:58.470 --> 00:07:00.690
And now, as you can see at the right hand side,

00:07:01.080 --> 00:07:04.020
this specific vulnerability has been tagged production.

00:07:05.080 --> 00:07:10.430
If you go back to the dashboard by clicking on the top left icon here,

00:07:10.430 --> 00:07:12.760
you can see that we have a tax called production.

00:07:13.010 --> 00:07:17.780
If you click on the tags, you can see all related vulnerabilities,

00:07:17.790 --> 00:07:19.940
which is one that we just tagged.

00:07:21.310 --> 00:07:24.740
So tagging can be an easy way to follow the progress of

00:07:24.740 --> 00:07:27.370
one or more specific vulnerabilities.

00:07:28.570 --> 00:07:29.870
That's it for this demo.

00:07:30.790 --> 00:07:35.980
In the next demo, let's use the API of open CV to search for vulnerabilities.
