start	end	text
4960	15700	Hi all. Hope everyone is doing well. In this circumstance, we are having a lot of things going in our life.
15700	20500	Apart from that, we are today eager to learn something to grow our knowledge.
20500	25420	I am thankful to Payment Village for giving me this opportunity to deliver this wonderful session.
25420	31960	And we are going to our session, Architecting Modern Payment Gateway in .NET Core with Azure.
31960	36980	Why I took this topic as a concern? What exactly today we are going to discuss?
36980	43280	Today we are going to discuss about how we are going to architect our payment gateways in .NET Core.
43280	50140	That is, here I am using Stripe. You can use some other third party tools like Payble, whatever it is.
50140	55480	Wherever we are using the bank credentials, wherever we are using the customer end details,
55480	61840	we need to follow the compliance rule so that we can have the security as well as we can prevent from data breach.
61840	69340	That is the main concern of security. That is the main concern of everyone to make the apps available to user end.
69340	74660	Security is the main thing that makes us important to work with the banking clients.
74660	80840	So, I choose this platform as a basic platform to implement the security.
80840	90080	At first, today as a demo, we are first going to see how exactly our payment gateway is designed in our .NET Core.
90080	97060	Every framework has its own style of doing the payment activities or some other activities.
97240	105360	So, .NET Core has some special architecture. So, we need to understand the architecture to implement the payment activity.
105400	111060	So, let's go to the next slide. I want to explain about myself. Who am I?
111060	115300	So, it may be fit to you to understand the titles. Very good.
115300	121260	I am Menaka Bhaskar Pillai. I am working as an associate software engineer at Accenture Digital.
121260	128440	And I am a C-Shop Corner MVP with Azure and .NET certified professional with a blogger and an international speaker.
128440	134760	You can reach out to me via my LinkedIn or Twitter as well as you can drop me mail. I will keep on checking.
134760	139320	For any doubts and clarification, you can approach me via any of this platform.
139320	148760	So, let's begin our slides of how we are going to explore our architecting the payment gateways in our .NET Core.
149000	152060	So, what we are going to discuss today?
152060	158300	The agenda is the main thing that gives the detail of what we are going to see in further upcoming slides.
158300	161860	Why payment security is important at its peak now?
161860	164620	What are the key features of payment app?
164620	167920	Why we go to .NET Core for payment integration?
167920	175380	Key components in Azure for secure payments, Azure payment processing environments, Azure security capabilities.
175380	179140	You can see two words as common, .NET Core and Azure.
179140	183820	Because as a .NET developer, we guys are not using .NET Framework.
183820	187260	Even it has the upgraded version that is similar to .NET Core.
187260	192640	.NET Core supports each and every OS that starts from Linux to Mac to Windows.
192640	195580	But .NET Framework supports only Windows.
195580	201040	So, that's the main reason we are facing many difficulty to implement the solution via .NET Framework.
201040	203220	So, we are migrating to .NET Core.
203220	207100	And another thing is .NET Core support the open source platform.
207100	210820	So, you can take the code and you can also contribute your code.
210820	215840	So, that's the only reason we are going behind the .NET Core.
215900	224060	Implementing security behind the scenes is very complicated compared to doing with .NET Core and Azure.
224060	229580	As a cloud provider, Azure is growing as a faster and faster in implementing the security.
229580	234920	It have lot of services that been used for securing your application.
235200	244680	For a business need or on the basics of business requirement, you can use any of the service that makes your application secure from each and every point.
244680	251920	Today, we are going to discuss the start and end wherever we can implement Azure in securing your web application.
251920	260040	Before that, we need to understand the architecture of how exactly the payment application can be implemented using the .NET Core.
260040	268820	So, I created a small demo to view you how the architecture of the payment application looks alike.
268820	274900	So, we can see the demo at the middle of the topic where .NET Core comes for the payment integration.
274900	277660	Before that, we can go to our next slide.
278580	281780	Why payment security is important at its peak?
281780	293720	You can see, payment security is the place where the customer is giving his card details for his owner whom he want to pay something.
293720	297380	My card is more valuable as compared to my life.
297380	305960	Any breach in data or any security incompetence that leads to the amount from my card that been disappeared.
305960	311200	And second thing, my entire details and personal and professional details can also be leaked.
311200	314100	That can impact my family circumstance also.
314100	321320	So, implementing security in payment gateway is very major and it's very trendful in today's concern.
321320	326560	Every banking securities are being highly concerned about implementing the security.
326560	332740	So, the usage of mobile payment expected to reach by dollar 503 billion by 2020.
332740	346200	So, what they are telling is, we are not going to the traditional approach of paying something with via our website where it is highly protected environment where we need to log in again and get to method transaction detail.
346200	351700	And again we are giving some detail to encrypt your details that you are the one who belong to that bank.
351700	356580	We are easily accessing everything from our mobile including the payment application.
356580	362640	I am, I can say like Paytm also, other application, everything been integrated with the payments.
362640	368100	So, I am ordering something in Flipkart that takes me directly to my GPay or another wallet.
368100	369940	So, I can add my payment.
369940	376280	So, nothing of the application nowadays they are developing is with payment, without payment is very rare.
376280	381620	So, the concentration of security also booming here to 2025.
382480	388800	In addition 75% of all financial transaction will be cashless by 2025.
388800	391520	You can consider now itself it's a Corona time.
391520	394000	We are having the payment application.
394000	396360	So, we are directly paying without card.
396360	402060	So, what exactly here happening is I don't need to depend on someone or my card to pay my cash.
402060	403960	I can pay by single click.
403960	408660	So, that is the concern that makes the security as important in today's scenario.
410200	413380	What are the key features of payment app?
413380	417240	Okay, I am developing an application that supports my payment.
417240	419720	What are the features I need?
419720	424500	What are the features I need to concern while creating or developing an application?
424500	427740	First thing, I should have the notification pop-up.
427740	437280	Whenever transaction appearing, I need to get notification via my mail, via my SMS, via other things that related to my payment.
437280	439180	So, notification is a primary concern.
439180	444480	So, I can track the amount that been debited or credited.
444480	446100	Billing and invoicing.
446100	451960	Billing and invoicing is a track about how much cash I been deposited, how much cash I been withdrawn.
452040	453780	Transaction history is a history.
453780	459140	So, I can trace this amount, this much amount I been spent, this much amount I been withdrawn.
459140	460820	So, fingerprint security.
460820	467120	This is a main security that need to be implemented in further upcoming apps if it is not been in before application.
467120	470780	So, fingerprint is like a, it is like, it is not similar to everyone.
470780	472900	So, it give the distinct of humans.
472900	475240	So, I can access via my fingerprint.
475240	476720	That is also main thing.
476780	478820	Cryptocurrency is a booming technology.
478820	483440	Without cryptocurrency, we cannot say like my application is secure or not secure.
483440	488020	So, bitcoins and cryptocurrency are leading in securing our application.
488720	492360	So, here comes our main topic.
492360	496060	Why we go to .NET Core for payment integration?
496060	500840	It provides a cloud ready, environmental based configuration system.
500840	508800	So, deploying my application which I designed for payment purpose is very easy if it is a .NET Core application.
508800	511080	Because everything are very customizable.
511080	516240	I don't need to write lot of code to maintain my application or to develop my application.
516240	523880	It is a very lightweight because .NET Core itself a lightweight and it stimulates the high performance with modular HTTP request.
523880	528200	.NET Core as I said before it is easy to maintain as well as update.
528200	534340	As in first slide itself I told why people are migrating even as a .NET developer from framework to .NET Core.
534340	541180	It is very, very easy to support every OS starting from Mac, Linux and Windows.
541180	544860	So, that is for very good to develop something in .NET Core.
544860	548980	So, I don't need to do a code reuse or copy my code to support the other system.
548980	550480	It is a scalable one.
550480	554100	So, I can able to scale my application as per my trends.
554100	558640	Easy to integrate inside and outside as well as on Google Cloud Platform.
558640	564780	Along with other Cloud Platform that using Agilnix or IIS or other supports.
565100	575240	So, let's see here itself a demo how exactly the architecture of the application via .NET Core will be looks like.
575240	580940	So, I am going to my coding session where I implemented a simple application.
580940	585000	That uses the payment third party tool.
585000	590220	So, see this is how my architecture looks like.
590220	594020	I choose .NET Core web MVC.
594020	597340	So, I have my views, model and controller folder.
597340	600820	Startup is the place where my code starts to work.
600820	605400	So, I need to register my middleware, HTTP, every action been performed here.
605400	611560	I am using third party tool called Stripe to integrate my payment in my application.
611760	619220	So, if you are using any tool for integration either it is a Paypal or Stripe or anything.
619220	621460	Just go to the official documentation.
621460	624700	You can get idea how to integrate with your SDK.
624700	626400	It's a Java or .NET Core.
626400	628460	Since I am doing .NET Framework.
628460	631940	I am just converted that to my .NET Core Platform.
631940	634180	So, since I am a .NET developer.
634180	638960	I just use the .NET Core for implementing the payment solutions.
639620	644360	So, what I am doing is for implementing the Stripe.
644360	645940	We need to have two things.
645940	648940	That are the environmental thing that remains constant.
648940	653380	Here I am declaring my environmental variable as in app setting.json.
653380	656700	So, it's easy for me to work on that.
656700	659460	Sorry, here it's app setting development.json.
659460	664060	It holds the two primary things like publishing key and my secret key.
664060	668560	This acts as a main thing while we are doing our transaction.
668560	675160	So, in order to use our keys from the app setting to our controller or model class.
675160	679680	We need to register or we need to consume this value to our startup class.
679680	684040	So, that it may be available to all of our services.
684040	686340	So, what I am doing here is.
686340	696990	I am just configuring my key here.
697130	701750	So, this is the thing that we, this is a common thing that you need to do.
701750	706470	Like I am getting the value of secret key that is a mandatory step to be done.
706470	712710	So, what I am doing is I already have my class that holds the method of set API key.
712710	715790	This sets the key API from the secret key.
715790	719930	After doing that I need to register my class that going to use.
719930	721530	Because tightly coupled class.
721530	724570	So, I just need to do this by using a class.
724570	730090	So, I just created a data class inside my model folder to use those keys.
730090	737010	So, those both the keys what you declared in app setting.json need to be declared here also with the same name.
737010	739810	So, here I want to bound my values.
739810	744190	So, from the app setting.json which is declared here.
745590	748130	So, I registering my class.
748130	751570	So, I can use my class via injection dependency.
751770	754470	So, configuration dot get section.
754470	759490	So, this get section holds the value of both the publish key as well as the secret key.
759510	763470	Once it is done I need to design my controller.
763470	765570	So, how my values been obtained at.
765710	768610	So, I am going to my controller class.
768650	777230	Here my controller class has the values of charge that been the both the things been originating from the form of stripe.
777230	780430	That I will show while I am running the application.
780530	784070	So, it contain the stripe email as well as the stripe token.
784130	787570	So, from this I am going to create the customer.
787570	795170	I am going to validate my customer like the email of the my email that been I am entering along with the source everything.
795290	798790	After that I am just paying some amount by fixed amount.
799030	804250	So, while the status code is succeeded I am just viewing my transaction is succeed.
804250	814530	So, it is very simple to implement because I just give my end points that is environmental variables in my app setting dot json that is development json.
814530	822070	And after that I am consuming my both of my keys like by using a tightly coupled class that I declared as a data class.
822070	828470	Once after that as I am just doing the action method by consuming from my view.
828470	835450	So, those are my email as well as the token from my view page into my controller.
839520	842420	See here I am just using that.
842520	849260	After that what I am doing I am just creating the transaction by means of what I want to do.
849260	855020	So, I just give the currency value description and everything the charge options I am just creating.
855020	856900	After that I am returning the status code.
856900	859820	Here you can validate whatever the thing you want.
859820	862560	Suppose you want to send some mail you can add those things.
862560	866980	It is a additional thing for the deeper application developer you can add those things also.
866980	871260	But it is not that much important if you going for a test purpose.
871260	876580	For a demo purpose I just want to show you how it works with a third party that is right.
876680	907730	So, I am just running it takes some time to load.
909070	925230	Yeah, so a simple line of code with very less complication is integrated my payment third party tool with my .net core MVC application.
925230	930130	So, what I am doing is I am just testing I already have one card.
930130	932630	So, I am just paying this.
933130	935970	So, my controller will hit here.
935970	946390	So, you can see from the form it takes the values of email as well as my stripe token.
946390	948200	That is a token that been generated.
948650	953110	Those text box been already designed by stripe we are just consuming.
953110	961090	So, just keep in mind giving the name should be very punctual compared to what exactly in your stripe.
961870	968210	So, after that I am creating the customer service object and a charge object, charge service object.
968210	973530	My customer is creating a new customer using a create operation.
973810	975490	Once again it is loaded.
975690	978430	You can see my customer while I am hoovering.
978430	984670	I have my customer ID and my object and some other detail if you want to give something you can add.
984670	986830	I just given the important things.
986830	991050	After that my charge service.
992570	996630	Here I will have my ID, amount, refunded.
996630	999150	You can add all those things if you want.
999550	1005630	If I am going to design a complete application not for a test I just want to give everything.
1005630	1007830	This is for the charge operations.
1007830	1016590	What kind of charging you are performing like you are charging based on your USD or INR depends upon your currency value.
1016590	1018910	So, this is a charge option that you need to be consider.
1018910	1024610	So, two things you need to consider that is a customer validation that is what we perform before creating the customer.
1024610	1031070	And you are consuming the value from your firm and by means of that you are creating that charge value.
1031310	1035310	So, after that the status code.
1035530	1040730	So, if it is validated I just want to go to the transaction ID.
1040730	1042670	This is for my display purpose.
1042670	1045810	If I want to display my transaction ID I can do here.
1045810	1047850	Or some other email triggering.
1047850	1050790	Every options can be performed after it is succeeded.
1050790	1053590	So, I can able to view this.
1054630	1057130	So, my code succeeded.
1057130	1059770	So, it is returning to view.
1061310	1062850	Transaction is succeeded.
1062850	1065210	Check email to view the receipt.
1066550	1068630	Okay, it's fine.
1068630	1074150	This is already the running application that I have already the stored value.
1074150	1076510	What if I want to do from the scratch?
1077370	1079850	Where I been written those kind of script?
1079850	1083310	What I am having in my view page?
1083310	1084830	So, I will show that also.
1084830	1086410	It's taking to load.
1100330	1102210	So, pay with card.
1105760	1109200	No, I do not want to do for the existing detail.
1109200	1111420	I want to do some cookie clear out or something.
1111420	1112520	So, it will clear.
1112520	1117880	Mostly for banking details we should not use this type of card registering.
1117880	1121940	Until unless it is necessary we should not have the practice of this.
1121940	1124980	Just I am going to give something like.
1133380	1137860	So, for testing purpose this have some test mode.
1147690	1151630	Take any card number from this for testing purpose.
1159960	1165120	So, give the year and because expiry date will be future.
1165120	1168240	So, give something in future dates.
1168240	1170160	And give any three numbers.
1170160	1171840	Because it's for testing.
1173100	1174060	Sorry.
1174840	1177020	And zip code is location code.
1181030	1182730	Do you remember me?
1182730	1184850	And it will ask you a phone number.
1185610	1189230	You can give your original number or something somewhere.
1189230	1194450	But don't give the usable number because it will trigger the start message to them.
1194630	1197410	So, give something that is not existing.
1197570	1200990	If it is validated only it will show you green tick.
1201170	1203030	So, it's validated.
1203990	1206230	So, I can just give continue.
1206930	1210090	Because I don't need to explore because I already explored that.
1211510	1214430	So, see the new code also.
1214430	1215670	Transaction has succeeded.
1216790	1218830	Check email to view the report.
1218830	1223370	So, my view page holds all my details.
1223810	1231010	So, view page will be like you need to add the view from customizable view or from the existing view.
1231010	1235170	I just use the existing views because I am showing everything in a single page today.
1235230	1237170	So, this is back.
1237170	1241430	I just need to add the script of this type along with the other future.
1241430	1244670	These are the futures that been displayed in your form.
1244670	1253250	So, if you want to add a zip local code or something you can add here or it is a inbuilt property.
1253250	1259610	So, you can choose auto property to set in your that you need to add some flavors to your form.
1259610	1261270	So, those things are customizable.
1261270	1262970	You can add those things.
1262970	1270310	That is guys this is how our payment gateway looks like using the integration with the third party tool.
1270310	1275690	Looks while we are constructing architecting in our .net core.
1275730	1277670	Do you feel this is secure?
1277670	1283010	I can develop like this and I can give to my customer and to yeah start doing your payment.
1283010	1285650	I just do a deployment in my production and give.
1285830	1289690	No, because this is not at all a secure one.
1289690	1296770	It is not even having authentication or the any token validation whether the user is existing or not existing.
1296770	1298890	And my values been already registered.
1298890	1300070	So, it is not secure.
1300070	1306030	So, how we are going to implement the security for the same application via Azure?
1306030	1312670	If you want to implement security for the same application with Azure, we have lot and lot of services.
1312670	1319790	As I said before based on your requirement based on your need decide what kind of security you want.
1319790	1323510	How much approach how much you want to deal with your application?
1323510	1326280	How much compliance your application need to be?
1326280	1334220	So, we are going to see some of the Azure service that is used to implement the security in your payment application.
1334220	1340240	And that is very much useful for architecting your application with wide level of security.
1340240	1342120	So, let us go to our slide.
1350270	1354610	So, key Azure component to secure your payments.
1354610	1356710	This is very limited guys.
1356710	1367350	If you go with Azure's complete services there are lot and lot of security components that can you can use in nook and corners of your application development.
1367350	1375790	But these are the very basic services that in ready in a normal payment application should needs need to be done.
1375790	1379910	So, the main thing is like Azure AD application.
1379910	1384510	I am doing something with my windows authentication that is up to my windows.
1384510	1389110	I cannot say after I am published to my Azure app service.
1389110	1392430	I deployed my application and after that I published my application.
1392430	1394730	I want to deal every user in a cloud.
1394730	1396990	I can use Azure AD application.
1396990	1400050	So, that it authenticate the user along with this password.
1400050	1406730	So, the particular person with the particular knowledge of particular thing he have can able to login.
1406730	1409250	Even that also provided by the cloud service.
1409250	1412630	That is quite good because my application is also already in my cloud.
1412630	1415590	And my application authentication is also in my cloud.
1415590	1420450	So, this is the first way to secure your application if you are using the payment gateways.
1420450	1422810	After that Azure key wallets.
1423050	1425150	Whenever my token is getting originated.
1425150	1427110	I want somewhere to store my token.
1427110	1429890	So, I can use my token to secure my application.
1429930	1433830	I cannot simply store my tokens that been originated in my application somewhere.
1433830	1435810	So, I can use again reuse again.
1435810	1437530	So, we can use Azure key wallet.
1437530	1441150	So, it is a secure platform you can keep everything.
1441150	1444390	It name itself and its symbol itself have the key symbol.
1444730	1448570	So, then Azure SQL always encrypted concept.
1448570	1455430	This is the main concept and main thing that need to be concerned while we are developing from our database end.
1455430	1458390	Because the encrypted concept is very useful.
1458390	1465590	While we are doing something as a backup knowledge of the transaction details or another thing we want to track for every application.
1465590	1469890	So, Azure SQL always encrypted concept is helps a lot.
1469890	1471770	Azure DDoS production.
1472010	1475130	This is a recent production that taken into the account.
1475130	1482810	Because DDoS production plays an important role of security breaches and other security danger and hazardous to your modern web application.
1482810	1493150	So, these are the 5 main core concept that need to be implemented while you are architecting your modern payment gateway or modern payment with any of the third party tools.
1493150	1502410	So, next thing is like this is I want to develop application that is completely secured from my back end to front end even from my data storage.
1502410	1504930	That I need to implement by means of Azure.
1504930	1507310	How can I do that? That's the thing.
1507310	1516270	So, they have every security features that need to be implemented while you are developing your application via Azure.
1516270	1528610	So, if you are using a database at your back end, just try to use the Azure key valid for protecting your all the necessary key values and everything that is like a tokens or something.
1528610	1534410	And there is a special thing for you governing your security of an application called Azure Security Center.
1534410	1537870	And as I told you the encrypt concept there at the SQL.
1537870	1540170	And Azure Blob storage is highly secured.
1540170	1547070	So, you can store your blog or any other file oriented data that is a transaction bills or anything in a blob storage.
1547070	1553610	OMS log analytics used to trace the logs, what are the logs you have been performed from your application level.
1553610	1559650	So, you can implement the security and application insight specially for monitoring your application.
1559650	1565050	So, any insecure communication or insecure request been getting into your application.
1565050	1566750	So, that it will product your application.
1567470	1573470	After that, coming to the Azure Active Directory and our role-based.
1573470	1576670	So, role-based authentication is very important.
1576670	1578970	It is like a role-based access control.
1578970	1583290	It is like what role exactly and how I can secure my application.
1583290	1585990	It is similar along with Azure AD also.
1585990	1588810	We can authenticate the user by AD service also.
1588810	1594030	Once I am coming to my front end, I am using the load balancer that is a payment gateways.
1594030	1604310	So, along with my app service environment, I can customize my application by adding my certificate, SSL certificate or other certificate.
1604310	1605750	So, that is very important.
1605750	1608850	And main thing is like application gateway.
1608850	1611610	Application gateway is very important.
1611610	1616610	Like I can implement by normal third party tool, we have oscillate.
1616610	1619770	If you are going with cloud, you already have the application gateway.
1619770	1623030	So, secure your application, balance your load.
1623030	1626010	Lot of request coming to one server, it is so hard.
1626010	1629990	So, the application gateway split the loads according to the servers.
1629990	1636350	So, it act as the direct contact to your client rather than to your API or some other.
1636350	1639290	So, your client do not need to approach directly.
1639310	1643990	So, all of these are producted by some of the thing is Azure DNS.
1644130	1647270	This is a very main concept if you are developing those things.
1647970	1655470	And along with the middle tier, everything I can be completely wrap up inside my DNS and environment.
1655490	1662630	So, I will have my storage policies along with other security policies and compliance and certified experts.
1662630	1668650	So, that makes my application productive if I am architecting my application via Azure services.
1668650	1673390	So, this is how the exact architecture of your application looks.
1673390	1679410	If you are implementing a normal .NET core application through your Azure service.
1679410	1683030	Guys, think after seeing this what you are getting into the knowledge like.
1683030	1687230	It is very easy and it is very cost conception is very less.
1687230	1689650	And other security breach also very less.
1689650	1695350	I will tell in further slide why my other things also like cost conception is less.
1695350	1698330	As well as why I can say this is a compliance one.
1698330	1702870	Why I can say believe this I can use this much things inside my application.
1702870	1712110	So, this is how exactly architecting the modern payment application via .NET core with Azure service looks like.
1712110	1717730	Use at least some of the services that is very important to your web application.
1717730	1720750	Where you are implementing the payment application things.
1720750	1723430	So, not all services you do need to use.
1723430	1728150	But there are some services you must need to use because of producting your application.
1728150	1730830	Even though you are not using this cloud service provider.
1730830	1737950	There is some other cloud service provider also where you need to use some of the things like authentication, load balancing, API gateway.
1737950	1747790	So, that will act as the productor of your application from malware or another hazardous things from hackers or some things.
1748070	1752190	So, data residency and boundaries.
1752190	1755290	Today we are going to discuss this data residency.
1755290	1757770	Why we need data residency?
1757870	1761170	Like our data been stored in somewhere.
1761230	1768290	So, whenever my data been lost I just need to depend on my own data center where I stored all my data.
1768290	1775310	By using or migrating to cloud it makes me available as a copy or reflect my copy to multiple region.
1775310	1780930	And it is accomplishing my multiple regions as a single availability zone to multiple availability zone.
1780930	1784270	So, inside a single region I will have multiple availability zone.
1784270	1787490	And all the availability zones are interlinked to each other.
1787490	1792350	And I will have another region that both my regions also interlinked to each other.
1792350	1800630	So, for accessing my request and approving my request for performing the action I do not need to depend on something a single availability zone.
1800630	1803790	I can perform everything with my facility perimeters.
1803790	1809630	So, I can have building entrance inside the building and data center floor.
1809630	1815870	So, it is very useful while we are designing our web application with lot of security features.
1815870	1821690	Everything inside a wrap of single thing is very hard to understand and very hard to product the data.
1821690	1826250	We need to keep our eye open to identify where it is, what it is.
1826250	1830450	So, just make and just make this things very clear.
1830450	1834450	Like that is the only reason we are migrating our things to cloud.
1834450	1843430	It provide lot of availability because data breach and data loss is not possible in cloud as we follow its policy futures.
1843430	1846470	So, this is one of the important slide to understand.
1847010	1849690	Azure SQL database security capabilities.
1849690	1855830	As we discussed in our few further slides like in our older slides I think so.
1855830	1858450	We see like encryption concept.
1858450	1861070	By means of this we have the customer data.
1861070	1866530	And we have the information production, threat production, access management and network security.
1866530	1872290	Think someone want to access your data need to pause all of the layer to access your data at the center.
1872290	1876730	That is quite that is even if he breaks the first network security.
1876730	1883470	He need to meet the access management after the threat production, after that information production to reach your customer data.
1883470	1890510	So, our how much our data is being producted inside our cloud by using the Azure SQL database security capabilities.
1890510	1897810	So, if you are working in a DB and it is very good to use DB security capabilities that is Azure security capabilities.
1897810	1901770	So, that makes our application to work good and secured.
1902290	1904390	Industry leading Azure security.
1904390	1908770	We can say why Azure is growing tremendously.
1909490	1913230	If I am choosing Azure as a service provider for me.
1913230	1919510	What is the difference of my cloud service with other services?
1919510	1920450	Why it is?
1920470	1926390	Because for a banking application or some other application where I am using my e-commerce application.
1926390	1928370	Where I am using my customer details.
1928370	1933550	It is not good to go with something which I have no knowledge.
1933550	1936410	Because data privacy is very important.
1936510	1938950	So, why I need to go to Azure?
1938950	1942630	Because the only thing is like it is not a one and only thing.
1942630	1947970	The main thing is like it they invested nearly 1 billion dollar annually.
1947970	1951370	So, for implementing the security future.
1951370	1953630	Not only for Azure security environment.
1953630	1957850	But for all the services in Azure for implementing the security.
1957850	1962150	So, each and every services of Azure implements the security.
1962150	1969250	So, that makes people who works in a normal application to the high end banking application secured in what they are using.
1969250	1972670	And this is around 3500 security expert.
1972670	1975930	And it has post a lot of compliance certification.
1975930	1982150	So, seeing the investment itself we can understand the security experts and the compliance certificate it got.
1982150	1985090	That makes us to move towards the cloud service provider.
1985090	1992190	So, we want to work in a secured environment where you need to keep everything in a very good maintained manner.
1992190	1993370	Well maintained manner.
1993370	1994870	In a secured manner.
1994890	2004030	You can start to implement your cloud service provider Azure to all your activity from back end, front end even at the middle tier also.
2004030	2006870	So, we ended the session.
2006870	2008610	I hope I made your day.
2008610	2010510	Like I just delivered my session.
2010510	2011770	This is a thank you slide.
2011770	2016030	I want to thank you all and everyone for listening my session.
2016030	2018050	For any doubts you can ask me.
2018050	2020130	I am here to clarify your doubt.
2020130	2023250	If the doubts be not satisfactory.
2023250	2025170	You want something to get more.
2025170	2027810	You can approach me again via my social platform.
2027810	2029090	So, I am available.
2029090	2031570	So, this is our today's session guys.
2031570	2034310	Thanks for giving an opportunity to Payment Village.
