1
00:00:00,300 --> 00:00:07,190
In this lecture, let's try to spend a few minutes on understanding what is security and why it is important.

2
00:00:07,230 --> 00:00:13,920
So before we jump into the discussion about spring security framework, I just wanted to spend a few

3
00:00:13,920 --> 00:00:17,710
minutes on the importance of security for developers.

4
00:00:17,850 --> 00:00:24,230
So if you ask me what is exactly the security for any Web application, I will answer to anyone.

5
00:00:24,480 --> 00:00:31,500
Security is for protecting your data that is staying inside your database or in the backend, along

6
00:00:31,500 --> 00:00:36,330
with whatever business logic that you wrote inside your Web applications.

7
00:00:36,360 --> 00:00:42,210
Like if you take any of our client applications which have JavaScript HTML, anyone can see that code.

8
00:00:42,330 --> 00:00:47,390
But coming to the back, end quote, it's very crucial to protect that.

9
00:00:47,400 --> 00:00:53,340
And at the same time, the data that is staying inside your database also we need to protect.

10
00:00:53,460 --> 00:00:59,560
So in order to do that, we follow many security measures which will be discussing in the future, like

11
00:00:59,580 --> 00:01:00,580
just so far.

12
00:01:00,600 --> 00:01:06,360
Now, please remember, security is like protecting your data and business logic present inside your

13
00:01:06,380 --> 00:01:07,470
Web applications.

14
00:01:07,620 --> 00:01:11,350
And next, security is a non-functional requirement.

15
00:01:11,370 --> 00:01:18,990
So if you ask me what is non-functional requirement and functional requirement, any client or any organization,

16
00:01:18,990 --> 00:01:24,780
if they want to build an application, they will write down their functional requirements, like I need

17
00:01:24,780 --> 00:01:27,540
to have so-and-so page so-and-so buttons.

18
00:01:27,690 --> 00:01:30,560
I need to accept so-and-so information from the user.

19
00:01:30,570 --> 00:01:36,750
So all those functional requirements they will define into the business requirement documents, whereas

20
00:01:36,990 --> 00:01:44,010
we also have equally important non-functional requirements like security, performance, scalability.

21
00:01:44,010 --> 00:01:51,000
So no client will specifically ask you or request you while building the application that my application

22
00:01:51,000 --> 00:01:56,080
need to perform very well and my application should have security inside it.

23
00:01:56,100 --> 00:02:03,090
It's our responsibility to consider that security or performance or scalability, whatever non-functional

24
00:02:03,090 --> 00:02:08,020
requirements that we have right from building the application from the scratch.

25
00:02:08,039 --> 00:02:14,250
So without meeting any non-functional requirements, even though if you deliver an application where

26
00:02:14,250 --> 00:02:17,650
it is working perfectly, your client will not accept.

27
00:02:17,670 --> 00:02:24,840
The reason is suppose if I deliver a bank application and it does not have any login or security for

28
00:02:24,840 --> 00:02:31,530
it, so anyone can see what my balance and anyone can transfer or withdraw the money without any authentication

29
00:02:31,560 --> 00:02:34,080
that definitely any client will not accept.

30
00:02:34,110 --> 00:02:38,100
So that's why police treat security as a non functional requirement.

31
00:02:38,100 --> 00:02:45,680
And consider right from your development face, as this is a very important consideration as a developer.

32
00:02:45,780 --> 00:02:51,810
And when I say security, there are different ways, are different types of security and how we secure

33
00:02:51,810 --> 00:02:58,320
our Web application, like Will, how firewall configurations inside our network, like if it is an

34
00:02:58,320 --> 00:03:04,710
internal application, we make sure no one is able to access from outside world by putting some firewall

35
00:03:04,710 --> 00:03:05,400
restrictions.

36
00:03:05,410 --> 00:03:07,200
So that is one kind of security.

37
00:03:07,320 --> 00:03:14,700
And at the same time, we also use his tips and SSL certificates to make sure that no one is tampering

38
00:03:14,700 --> 00:03:18,730
the data when a client is sending data to back and server.

39
00:03:18,870 --> 00:03:20,820
And that is one kind of security.

40
00:03:20,820 --> 00:03:27,240
And at the same time, we also have authentication and authorization to make sure our application will

41
00:03:27,240 --> 00:03:29,760
be used by only authenticated users.

42
00:03:29,940 --> 00:03:35,370
And every authenticated user can perform actions on what he's authorized to do.

43
00:03:35,370 --> 00:03:42,360
So Spring Security Framework will help us in implementing a authentication and authorization inside

44
00:03:42,360 --> 00:03:43,530
our Web applications.

45
00:03:43,680 --> 00:03:47,370
So don't worry about what's the difference between authentication and authorization.

46
00:03:47,520 --> 00:03:50,520
We'll be discussing all these details in the coming lecture's.

47
00:03:50,640 --> 00:03:53,430
So you may ask me, like, why security is important.

48
00:03:53,520 --> 00:03:58,410
So without security you will lose data and money.

49
00:03:58,410 --> 00:04:04,950
Also, like if you deliver a bank application where it does not have proper security implemented, like

50
00:04:04,980 --> 00:04:12,240
as a customer, I can see other balances or someone can transfer money from my account without my authorization,

51
00:04:12,390 --> 00:04:14,790
then it's not a valid and good application.

52
00:04:14,910 --> 00:04:20,459
Then definitely that bank will lose the customer's trust that they have built over the years.

53
00:04:20,459 --> 00:04:26,640
So due to this reason, police always treat security as equally important, like your business logic,

54
00:04:26,640 --> 00:04:33,270
because without security you will end up having legal issues, brand reputation issues, and you'll

55
00:04:33,270 --> 00:04:36,210
also lose millions and billions of money.

56
00:04:36,420 --> 00:04:42,390
And while implementing security inside your applications, we should also consider how to acquire the

57
00:04:42,390 --> 00:04:47,640
most common attacks like CSR for tech, broken authentication costs, attacks.

58
00:04:47,760 --> 00:04:53,340
So all this kind of most common attacks we should be able to handle inside our application with the

59
00:04:53,340 --> 00:04:54,360
help of security.

60
00:04:54,450 --> 00:04:59,520
So don't worry, we're going to discuss what are the most common attacks like what is sort of what is.

61
00:05:00,240 --> 00:05:06,540
And how to protect our application using spring security in the coming lectures, for now, please try

62
00:05:06,540 --> 00:05:10,770
to understand that security is very important inside our application.

63
00:05:10,890 --> 00:05:17,880
So due to that reason, only Spring DMN came up for a dedicated framework focusing on security, along

64
00:05:17,880 --> 00:05:24,960
with the name Spring Security, which will make developer architects lives easy to achieve authentication

65
00:05:24,960 --> 00:05:27,420
and authorization inside our web applications.

66
00:05:27,570 --> 00:05:33,180
I hope this is very clear to you now on why security is important for any web application.

67
00:05:33,360 --> 00:05:33,840
Thank you.

68
00:05:33,850 --> 00:05:35,850
And I'll see you in the next lecture by.

