The title of our sermon this morning is Are You in the Faith? Are You in the Faith? Our text is 2 Corinthians chapter 13 verses 5 through 10. Are You in the Faith? As we come to this text, 2 Corinthians chapter 13, specifically this paragraph from verse 5 and verse 10, we realize together that we've spent nearly two years now in the second letter of Paul to this church at Corinth. It's amazing to think how quickly the time has gone for what a blessed time it's been. And as I think back over the last two years together, being able to study this letter in such detail as we have by the grace of God, there are several things about this study that I've been extremely grateful for. I pray that you've been blessed by the study that you're grateful as well. This is the Lord's blessing to us. And I'm very grateful for many things about this letter, the second section of the book. In chapter 2 verse 14 through chapter 7 really, one of my favorite sections of text in all the Bible for its theology. Just wonderful, beautiful, glorious, Christ exalting theology. We have the fullest treatment of grace-fueled, Christ-motivated giving anywhere in the New Testament, given in chapters 8 and 9. The perspective that we've been given on Christians, suffering, the recurring theme throughout the letter of strength through weakness, the whole letter really start to finish. A beautiful, wonderful exposition of Christian ministry. Not just the ministry of the pastor, but the ministry of everyone called in the name of Christ to serve the Lord's church. What we're here in the church to do, and why we are here in the church doing it, it's beautifully portrayed throughout this letter. The church at Corinth would have been a tough pastoral assignment. So often agonizing. The agony compounded by heartbreak and heartache. The people were saved out of the midst of pagan idolatry. They were saved to serve in a city that was overrun by pagan idolatry. It's not unlike the context that we find ourselves in today. But the thing that has been most impactful to me I think in studying the letter of 2 Corinthians has been the example of the apostle Paul. What a tremendous example that Paul is to believers and to pastors. The letter opens in chapter 1 with the account of the trial that Paul faced in ministry where Paul thought for sure that he was going to die. What was Paul's response to that trial? It was the Lord teaching us not to trust in ourselves, but to trust in God who raises the dead. That pretty much sums up Paul's outlook in Christian ministry. It sums up Paul's outlook on life, doesn't it? We are always powerless, and he's the one who raises the dead. It's a wondrous testimony of faith. Paul wholeheartedly, entirelessly loved the congregation in Corinth. He had begotten them through the gospel. They were like his spiritual children and Paul likened himself as to his spiritual father among them. So he labored for them. He'd labored for them. 1 Corinthians chapter 4 verse 11 he said to them, to the present hour we both hunger and thirst. We are poorly clothed and beaten and homeless. Why? Right? We labor, Paul says, working with our own hands. Being reviled we bless. Being persecuted we endure. Being defamed we entreat. We have been made as the filth of the world, the off-scouring of all things until now. So I do not write these things to shame you. But as my beloved children, I warn you, for though you might have 10,000 instructors in Christ, yet you do not have many fathers. I'm it, Paul says, right? For in Christ Jesus I have begotten you through the gospel. That's all Paul loved them. Paul often warned them. Why did Paul warn them? Because he loved them. He warned them because he loved them. He knew what was at stake. He knew the spiritual danger that they were in. He knew the precipice of apostasy on which they seemingly so often stood. And he knew what the outcome would be if they persisted in their sin. He warned them. He exhorted them. He pleaded with them. He implored them. He endured their disrespect. He endured their doubts. He endured their distrust. And when they no longer wanted to hear from him, he patiently preached truth to them and continued to preach truth and continued to preach truth. When false teachers came in to Corinth and lured their hearts away from him, Paul endured their heart-hearted, cold-hearted distance and said, I will gladly spend and be spent for your souls, even though the more abundantly that I love you, the less that I'm loved. But more, more than merely enduring all their shameful sin and failure, it was obvious that Paul tirelessly loved them through it, not simply endured it, but loved them through it and labored to see it reversed, ministering to them with sacrificial love with unwavering faith, with tremendous patience, uncompromising commitment, unparalleled devotion of the Lord into the Lord's cause, a thoroughly Christ-centered focus in everything that he's doing, doing whatever that he can for their joy, for their good, working together with them for their joy. And it's with an eye to this example among them that Paul says to them, and to us, imitate me, imitate me, imitate me as I imitate Christ, right, imitate me. And Paul has been through a lot with this church at Corinth. We saw last week that he's preparing to visit with them a third time now, laboring with them again. Paul again is concerned about where they are spiritually. He's concerned about what condition he's going to find them in when he shows up the third time. But he has been long suffering with them, a tremendous example of patience. But there's a point, Paul knows it, we know it. There's a point at which further patience becomes counterproductive. And so Paul applies a principle from the law to his own experience with the Corinthians. He says, this will be my third visit to you, and by the mouth of two or three witnesses, every word, every judgment shall be established. I'm writing to those, Paul says, who have been persisting in sin all this time. Writing to you who are unrepentant, and to all the rest, that when I come this time I must take action. I will not spare. It's for their good. Why does Paul do this? Because he loves them. Why does Paul do this? He loves the church. He loves the Lord. He loves the Lord's people. It's necessary work. Even these statements, statements that would sound harsh, statements that would sound authoritarian to the godless, this godless world, statements that would sound harsh or authoritarian to professing Christians that have a whimsical pie in the sky kind of notion of what genuine love is. Even though these statements would sound harsh to them, these statements reflect the love of Christ to this wayward, beleaguered church. It's the it's the grace and mercy of God to them yet again. It's in this love and in this care for these people that motivates the apostle Paul to his next statement in chapter 13, verse 5, where Paul says there, examine yourselves. Examine yourselves as to whether you are in the faith. Test yourselves. Do you not yourselves know that Jesus Christ is in you unless indeed you are disqualified? And many professing Christians today would respond to that kind of a question with a kind of self-righteous indignation, right?   And that response actually communicates a lot about where they are spiritually, right? Communicates a lot about what their spiritual condition actually is. Some would say that we should never question our salvation. Why would you ever question your salvation? It's like a failure of faith to do so. If you question your salvation, the devil, the devil is the one who makes us doubt, right? You shouldn't question your salvation. And if you question your salvation and it's a failure of faith, Paul is commanding them to examine themselves in our text. For others, for many, to question their salvation or to call for a self-examination is to hammer away, hammer and chisel at the self-justifying defenses that they have carefully built up around their deceitful and deceiving hearts. You see? Spend our time building up concrete walls around our heart to keep us from the truth. They've walled themselves in behind a defense of deception and a call to self-examination, question about the fruits of their salvation, chips away at that wall. Paul's concern for the Corinthians, of course, is pastoral. Why does he do this? Because he loves them. It is the loving, right and good thing to do. It's loving, right and good for Paul to have brought them to this point of self-examination. It's loving, right and good for us to come to a point of self-examination in our own experience. We'll see that in the text. So what does Paul do then? Paul confronts them in the text with a pastoral imperative in verses five and six, and then he encourages them with a pastor's prayer in verses seven through ten, a pastoral imperative, a pastor's imperative in verses five through six, and then encouraging them with his prayer for them in seven through ten. Consider first with me now Paul's pastoral imperative in verses five through six. Look at verse five with me. Paul says, examine yourselves as to whether you are in the faith. Test yourselves. Do you not know yourselves that Jesus Christ is in you unless indeed you are disqualified? Now Paul is calling the Corinthian church to self-examination, to self-examination. To understand this call, the first thing that we want to do is to understand Paul's purpose for doing that. We want to understand Paul's purpose, and then we want to consider together a personal application. First Paul's purpose and then a personal application. Thinking about our context, what is Paul's purpose here for calling the Corinthians to examine themselves? If you look at verse five, the verbs there are imperatives, they're commands. Paul is commanding them, examine yourself, test yourselves. In the Greek, the word order is reversed for emphasis, yourselves examine, yourselves test. What is Paul's purpose here? Think with me. Paul's ministry from the beginning really in Corinth has been under attack by false teachers who have infiltrated the church. False teachers are attacking, assaulting, the reputation, the credibility, the ministry of the Apostle Paul among the people at that church. These false apostles, these ministers of Satan have been undermining Paul all along. Their accusations against him have taken their toll and the people themselves now have begun to doubt. They've begun to question Paul's authenticity as a legitimate apostle, as the Lord's apostle. They have begun to put him to the test, so to speak. They've begun to put him to the test. The false teachers in many in Corinth have begun an examination of the Apostle Paul. Paul essentially is saying here, if you want proof that I am an apostle, then look no further than yourselves. Rather than putting me to the test, Paul says, test yourselves. Rather than looking for evidence in me, yourselves examine. Do you see? Now in verse 5, verse 5 is connected to verse 3 above, where in verse 3, since you seek a proof of Christ speaking in me, that's what they're doing, they're testing Paul, examining Paul to see if there's a proof of Christ speaking in him, since you seek a proof of Christ speaking in me, examine yourselves. Test yourselves. Calvin said this, the Lord has shown his power in Paul's preaching in such a manner that it could be no longer doubtful or obscure to the Corinthians if they were not altogether stupid.  They're going to figure it out. Where did the faith come from? Where did it come from? It came from the Lord through the preaching of Paul. Is Jesus Christ in you? How did he get there? He got there by the Spirit through the preaching of the Apostle Paul. You want proof that the Lord is at work in my ministry, Paul says? Then yourselves examine. Do you see the context? Now he said essentially the same thing in chapter 3, verse 1 where he says in chapter 3, verse 1, he says, do we begin again to commend ourselves? Or do we need as some others epistles of commendation to you or letters of commendation from you? Paul says you are our epistle written in our hearts known and read by all men. Clearly you, Paul says, are an epistle of the Lord Jesus Christ, ministered by us, written not with ink, but by the Spirit of the living God, not on tablets of stone, but on tablets of flesh, that is tablets of the heart. You want proof that the Lord is at work through me, Paul says? Look to yourselves. You want proof. You want proof. You want evidence that the Lord is at work in this church? Then look to yourselves. Look to yourselves, Paul would say. Are you making progress in the faith? Then you cannot deny it. Do you see the fruits of the Spirit in the lives of the people here? Then praise the Lord. Be encouraged. Be encouraged. Did you get converted on the preaching and teaching of the church here? Well then how in the world did that happen? It's because of the Spirit of God is at work here, amen? Paul says you want proof of my apostleship, verse 5, examine yourselves as to whether you are in the faith. Test yourselves. As similar to chapter 11, verse 4, prior to the preaching of the false teachers in Corinth, they had no other Jesus, but the one that Paul had preached to them. They had no other Spirit, but the one that they had received through the preaching of God's Word by the apostle Paul. They had no other gospel that they had accepted, but the one that Paul had proclaimed to them. So Paul says essentially, examine your own condition rather than picking at mine, and there you'll find your answer. And Paul asks them a question. And when Paul asks them a question here, Paul assumes the answer. He believes the best about them. He says, do you not know yourselves that Jesus Christ is in you? Paul essentially is saying, of course you do. Unless indeed you are disqualified. Unless, of course, you are adachimus, disqualified. Even that word adachimus itself isn't negative, right? It has in mind testing the genuineness of something with the intention of finding it true, right? With the intention of proving it, finding it qualified. That may seem amazing to some that Paul has such a positive outlook like this, considering the church at Corinth, but there's no mistaking Paul's outlook. He believes the best about them. After all the heartache that they've caused him by their sin, after all the ways in which they failed the Lord, all the ways in which they've failed the apostle Paul, all the ways in which they failed the church, there they are following the Lord in Corinth. There they are persevering in faith, following the Lord in Corinth. And Paul believes the best about them. And Paul believes the best about them. Paul's not leveling as it were, right? The 50-pound hammer against them, Paul believes the best about them. And believing that they will undoubtedly come to a correct conclusion about their status in the faith, Paul adds this then in verse 6. But I trust the word El Pizo is better translated hope. I hope, Paul says then, that you will know, that word's a compound word, it has the sense of knowing for certain, without a doubt, that we are not disqualified. But I hope that you will know for certain, Paul says, that we are not disqualified. In other words, if you find, Paul says if you find that you in fact are in the faith, if you find that Jesus Christ is in fact in you, then I trust you will draw the inevitable conclusion. I trust that you'll make the proper connection and know for certain that we then are genuine also. If they pass the test, then Paul passes the test. Do you see? They're bound up in this together. Now that's Paul's purpose for the command, for the imperative. Paul has that purpose in mind as he calls the church at Corinth to examine themselves. That's the point. I remember years ago, being away to conference, spending the Lord's day with brothers and sisters at a godly mature biblical church, a church that we love. Sweet people, sweet fellowship, they love the Lord. They love the Lord's word. They love the preaching there. But they had not long before lost a beloved pastor, a pastor that had been there a very long time, a man that they loved dearly. This pastor had been replaced by a godly man, a good brother, a faithful brother, faithful pastor. But things were different, right? He was different. The circumstances were different. A young lady that I was talking with didn't know how to process or even really understand the sense of loss that she felt at her pastor moving away and that things were now different, just didn't understand the feeling. And so she wondered to herself, as probably others may have as well, that maybe the spirit of God was no longer at work in that church, that the spirit of God had left the church, no longer at work there. She was fearful, she was discouraged by that feeling. And so I asked her, we're sitting down and I asked her, I said, do you have the spirit? The simple question, are there others here with the spirit? In other words, the church is not a building. The church is not a building. The church is the people of God with Christ in them, the spirit of God in dwelling them and working in them and through them and among them. That's the church. So I said, do you have the spirit? You say, well, yes. Do others here have the spirit? Do you see the fruits of the spirit at work? Wind blows where it wishes, right? You hear the sound of it, cannot tell where it comes from, where it goes. So is everyone, the Lord says, who is born of God's spirit. Now I'm not talking here about emotional hype. We know the difference, don't we? Those that feel like the spirit is moving because you feel all warm inside when the music is playing. Churches by the thousands, professing Christians by the millions confuse a work of God's spirit with mere emotionalism. We're not talking about mere emotionalism. We're not talking about emotional hype. We're also not talking about the guy who's manipulating the masses to get a bunch of lost people down an aisle to ask Jesus in their heart. We're not talking about hype. And then he boasts in a work of the Lord when 300 people in a year get saved by that, not saved by the Lord, saved by that. And then 75% of the people who say they got saved by that aren't even attending church any longer. We're not talking about hype. I'm talking about real fruits of the spirit. Paul is referring to real, genuine, spirit wrought fruits in the Lord's people, in the Lord's church, a love for God's Word, a hatred for sin, a hatred for all those things that God hates, a love for all those things that God loves, a heart for evangelism, a heart to see sinners saved, an affection for God's people, a devotion to the Lord's work, joyful, heart-faith-filled obedience to God's commands, loving, accountable, involvement, fellowship in the lives of God's people, increasing holiness, maturity, increasing knowledge, increasing faith, increasing love, a bounding in the grace of God. That's the fruit of the spirit. It was a bitter old curmudgeon that used to attend our church years ago. We didn't do the things around here the way that he thought they should be done. And so he'd walk around the church telling people that the spirit of God wasn't here. Spirit of God has left this church. Spirit of God is not at work at this church. He thought he was being faithful by overseeing a ministry of discouragement in the Lord's church. That's not faithful. That's ungodly. That's ungodly. That's despising the grace of God. Look around, folks. Right? Be encouraged. Be encouraged. Don't just be encouraged. Be grateful. Be grateful, right? Praise the Lord for his grace. Praise the Lord for a work of his spirit in our church amongst his people here. Right? That's Paul's point. Paul is calling them to self-examination to see what the Lord has done in and through them. And Paul trusts that when they recognize a work of God's spirit in them, among them, and through them, they're going to connect that with the preaching and teaching of the apostle Paul. Paul. They are a living epistle ministered by Paul. Be grateful. Be encouraged. The spirit of God is at work here. But now, think with me, what about you personally? What about you personally? That command for the Corinthians to examine themselves, to test themselves, wasn't merely a command to some nebulous corporate entity called the church. It's a command to individuals in the body of Christ. Test yourselves. Examine yourselves. Paul had a distinct purpose in calling the Corinthians to a sober self-examination. He believed that, by and large, they would come to a positive conclusion regarding their condition, their spiritual state. But the test, doesn't it, certainly holds out the possibility that one may be found to be a document disqualified. That in mind, those are serious stakes. And so Paul's command to self-examination isn't to be taken lightly. It's not to be taken lightly. The question can't be passed over trivially. Every sober-minded believer, follower of the Lord Jesus Christ, should take this seriously. Paul may have assumed the best about the Corinthians, but we're not to be presumptuous about the state of our own soul. We'll see from the text why. Far too much is at stake. Far too much is at stake. We're talking about eternity, heaven and hell, life and death. This is a critically important test. One indication that this is a critically important test is found in the nature of the question. It's found in the nature of the question. What is the nature of the question that Paul is asking? Paul essentially commands the question, are you in the faith? Is Christ Jesus in you? In other words, do you belong to him? Has he saved you? Have you been delivered from the power of darkness and conveyed into the kingdom of the Son of his love?  Are you in the faith? Is Christ Jesus in you? There's ultimately nothing more important than asking that question, asking and answering that question. Amen? Is there? Now some would say, well that Paul referring here to the faith, he's referring to the objective body of revealed truth, the content of our faith. Right? The content of our faith. Do you objectively believe what the Bible says? Well, if you say that you believe that objective set of facts, well then Christ is in you. You believe that's all that's necessary? You pass the test? Listen, that's nothing more than mere intellectual ascent. That's nothing more than mere mental agreement with a set of facts presented in the text of Scripture. Mental ascent, they hear me now, listen, mental ascent, intellectual agreement falls short, woefully short of genuine saving faith in the Lord Jesus Christ. It's not simply agreeing with a set of facts. Even the demons believe those facts and they tremble. They're terrified of the judgment that awaits them. The nature of this test that Paul is calling us to would certainly include the objective content of our faith. It certainly matters what we say that we believe. That's definitely important, but Paul has something more in mind here than simply the content of our faith. Paul's point is made clear by the nature of the question, the nature of the question. The command to examine yourselves as to whether you are in the faith is clarified by the following question. Do you not know yourselves that Jesus Christ is in you? In other words, being in the faith means that Jesus Christ is in you. That's getting at the heart of the issue, isn't it? It's getting at the heart of the issue. Is Jesus Christ in me? Is Jesus Christ in you? Am I in vital union with the Lord Jesus Christ? Does he live within me, as the Bible says, by the Spirit? Am I a branch that is connected to the vine? Hear Calvin again. Our whole salvation and all its parts are comprehended in Christ. None of our salvation and none of its parts are comprehended apart from Him. It's all found in Him. Am I in union with Christ? That's the nature of the question that Paul is asking. That's the nature of the question. We must understand that as long as Christ remains outside of us and we are separated from Him, all that He has suffered and all that He has done for the salvation of the human race remains useless and of no value to us. Therefore, to share with us what He has received from the Father, He had to become ours and to dwell within us, Christ in us, amen. We also in turn are said to be engrafted into Him and to have put on Christ. If we are not in Christ, if we are not in Christ, and if He is not in us, if we are not in vital union with Him, then we have no place, no part of His death on the cross for sinners. If He is not in us, we are not in Him, if we are not in vital union with the Lord Jesus Christ, we have no part of His perfect righteousness, no part with His atoning work. We have no part in His resurrection from the dead. How is it that will be raised? Will be raised in Him, amen? If Christ is not in us and we are not in vital union with Him, we are not justified. We are not sanctified. We are not glorified. We're not saved apart from union with the Lord Jesus Christ, apart from the Lord Jesus Christ being in us. We're not adopted.   It's just that clear. It's a matter of life and death, do you see? A matter of life and death. It's amazing to me how lost people, people outside of Christ, people without the Spirit, continuously labor to suppress that truth in their unrighteousness. It is just that clear, just that simple.   Why aren't people scrambling to figure it out? Am I in Him? Is He in me? Has He saved my wretched soul or not? The stakes are high. It is eternity that is in question. Examine yourselves, test yourselves whether you're in the faith. Do you not know that Christ Jesus is in you? Do you? Unless you are disqualified? It's a vital, critical question. And yet in self-justifying defense of some religious experience or some profession of faith or some prayer that was prayed or some sacrament that was taken, people will fight tooth and nail to avoid the implications of that question. What does it mean? What does it mean for Christ Jesus to be in us? What does it mean to be in vital union with Him? What does it look like? What does the Bible say? You're not going to find the truth of that in your own heart.  You can't make it up. The Bible tells us what it looks like. The Bible tells us what it is. The Bible tells us what it means. We've got to go there for the answer. And listen, your soul depends on it. But now, right now, considering that question, we've moved from something objective, like the objective content of our faith. Do you believe these facts? A lot of people can say yes. I believe them. Many will say no, I don't. But that's pretty objective. It's pretty objective. We've moved now from something objective to something far more subjective. Something far more subjective. How do I know? How do I know that Jesus Christ is in me? How do I know that I'm in vital union with Him? Notice that Paul isn't asking you if you sincerely prayed some prayer to receive Christ. He's not asking that question. He's not asking that question. Who cares? That's not the point. We don't even know our own hearts.  Are you going to base it on that? Paul isn't asking you if you sincerely prayed a prayer or received Christ or asked Jesus into your heart, right? People often want to lay hold of something more objective so they can hang their hat on that. So they can embrace that and holding on to that gives them a sense of security. And if you start chipping away at that, they get defensive. They can even get hostile. They can even get angry. Paul isn't asking that. Paul isn't pointing to that. For many, for many, self-examination means looking back to some prayer that they prayed. Looking back at some religious experience that they had, relying on the sincerity of some profession of faith, relying upon the efficacy of some religious ritual that they performed, something that happens, something that they did. They look back and they place their security in that. If that was real, I'm saved and I'm okay. And they labor to assure themselves with those facts, those experiences, relying on feelings that they believe they have about Jesus or God or His Word experiencing sorrow or conviction over sin, feeling guilt or shame because of sin. Because I'm guilty, I know the Lord has saved me. I'm okay. Living an outwardly moral life because I put down some bad habits and I picked up some good ones, now I'm okay. I know I'm saved. I know I'm okay. Hanging their hat on that, simply believing the truth because they fear God's judgment, being outwardly religious or believing that because of all that, they have eternal life. Paul isn't asking about any of that. Paul isn't pointing to any of that. To look to a prayer or some religious activity for title to eternal life is to put your faith in the shifting sand of some human experience and not upon the bedrock that is the person and work of the Lord Jesus Christ alone. Do you see? It is a false faith. It is a misplaced faith. And listen, the people who peddle that kind of deception are peddling a false gospel and a false faith and they are false teachers. It is false. It's an ingenious masterful construction of our enemy to deceive you away from the truth. Is Christ Jesus in you? Are you in vital union with him by God's spirit? That's the question. Do you see? That's the point. Are you in him and is he in you? Can you say I am his and he is mine? Test of authenticity is this. Is Jesus Christ in you? Because the answer to that question is more subjective. The answer is open to abuse, open to deception, open to delusion. So one, listen, one, the nature of the question, that's the question, right? The nature of the question is an indication of how critically important this test is. Secondly, the nature of man's deception is also an indication of how critically important this test is, the nature of man's deception. The Lord himself reminds us, turn with me to Matthew chapter 7. The Lord himself reminds us of this in the Sermon on the Mount in Matthew chapter 7. He reminds us of the importance of self-examination, reminds us of our propensity to deceiving ourselves. In the Sermon on the Mount, Matthew chapter 7, look beginning with me at verse 13. First, the Lord opens by reminding us of the danger. The danger of deception reminds us how critically important this question is. Look at verse 13. The Lord says, enter by the narrow gate, for wide is the gate, and broad is the way that leads to destruction. And there are many who go in by it. We'll see that the many who go in by that gate are many who will call him Lord. These aren't the atheists and agnostics and God haters. These are many who call the Lord Lord. They're entering in through the broad gate. Narrow is the gate. Wide is the gate, broad is the way that leads to destruction, and there are many who go in by it, because narrow is the gate, difficult is the way which leads to life, and there are few who find it. Then, communicating with us about the danger, the danger of understanding this rightly, the Lord gives us the evidence that we need then to answer the very important question. Look at verse 15. Beware of false prophets who come to you in sheep's clothing. Inwardly, they are ravenous wolves, something very profound. Verse 16, you will know them by their fruits. You'll know them by their fruits. Do men gather grapes from thorn bushes or figs from thistles? Even so, every good tree bears good fruit. Axiomatic, right? Every good tree bears good fruit, but a bad tree bears bad fruit. A good tree cannot bear bad fruit, nor can a bad tree bear good fruit. Every tree that does not bear good fruit is cut down and thrown into the fire. By their fruits, good or bad, by their fruits, you will know them. Then he reminds us, then he reminds us of the danger of deception. Verse 21, not everyone who says to me, Lord, Lord, shall enter the kingdom of heaven, but he who does the will of my Father in heaven. Many will say to me in that day, Lord, Lord, have we not prophesied in your name? Cast out demons in your name, done many wonders in your name. Now listen, that is a, it's not a comprehensive list, that's a representative list. There are many who will say before him who'd never cast out a demon, who've never done any wonders in his name, but certainly have prayed a prayer, went to church every Sunday, served as a deacon, was a pastor. Many will say to me in that day, Lord, Lord, didn't I meet it when I said that prayer? Wasn't I at mass every week, twice a week, three times a week? Didn't I do all of these things, Lord, in your name? Then I will declare to them, verse 23, I never knew you. Depart from me, you who practice lawlessness, that which is produced in the life of a person outside the spirit of God is characterized as lawlessness. Only that produced in a person by the work of God, by his spirit is that which is righteous in his sight, that which is performed in a vital union with his son. Only that could be considered righteous in God's sight. I never knew you. Depart from me, you who practice lawlessness. Are you in the faith? Are you in the faith? Is Jesus Christ in you? The question may be more subjective, but the Lord gives objective evidence for seeking an answer. He says you will know them by their fruits. You will know them by their fruits. The Bible teaches that these fruits are produced by Jesus Christ in you by the spirit. These fruits are produced by his spirit. The Lord says, listen, in John chapter 15, verse four, abide in me, the Lord says, and I in you as the branch cannot bear fruit of itself unless it abides in the vine. Neither can you bear fruit of yourself unless you abide in me. I am the vine. You are the branches. He who abides in me and I in him bears much fruit. For without me, you can do nothing. If anyone does not abide in me, he is cast out as a branch and is withered and they gather them and they throw them into the fire and they are burned. Are you abiding in the vine? First John chapter four, verse 13, by this we know that we abide in him and he in us because he has given us his spirit. We know that we abide in him because he has given us his spirit. Paul says in Galatians chapter two, verse 20, it is no longer I who live, but Christ lives in me. Do you see? If by the spirit you are producing the fruits of the spirit, Jesus Christ is in you by the spirit. Paul says this again in Romans chapter eight, verse 16. Listen, the spirit himself bears witness with our spirit that we are children of God. When Paul asks the question in 2nd Corinthians chapter 13, verse five, do you not know that Christ is in you? Paul has confidence in them that they will see God's spirit at work in them confirming spirit wrought fruits in them giving them an assurance that they are children of God. Do you see? That's how it works together. Assurance comes by the spirit. Paul feels confident about those in Corinth that they're going to find a work of the spirit of God within them and is confident that they're going to find themselves to be in Christ as a result. The spirit himself bears witness with our spirit that we are children of God and if children then we are heirs, heirs of God, joint heirs with Christ if indeed we suffer with him that we may be also glorified together. Assurance comes from the spirit of God. We'll look at the evidence in more detail as well as the rest of our text Lord willing next week. For now consider this with me. There are some of you in this room who are in the faith genuinely truly Christ is in you. You are accepted in the beloved. You are trusting in the finished work of Jesus Christ alone for salvation. You are partakers of the divine nature, partakers of the heavenly calling. Your citizenship is in heaven and you eagerly await the Savior. But there are others of you in this room who are not in the faith. Jesus Christ is not in you. You may believe that he is and your belief may be misplaced. You may be deceived about that which points to whether or not Jesus Christ is in you. You may have been deceiving yourself. You may know that he's not. I've not turned for my sin. I've not put my faith and trust in him. What are you waiting for? Your soul is precious. Others of you though are deceived about that. You've built up a lie. Comforted yourself with a placebo. But you are under the just condemnation and righteous wrath of a holy God who will not acquit the guilty. The answer to safeguard against deception is faith alone in Christ alone. Stop living for yourself. Put faith and trust alone in the Lord Jesus Christ alone. If you come to him, he will in no wise cast you out. Put your faith in him. Faith in him is the safeguard against deception. The spirit of God preserves his people in the faith. The spirit of God is the guarantee of our inheritance. We must have Christ in us by his spirit. We must have the spirit of God. The answer to safeguard against deception is faith in the Lord Jesus Christ. We'll look at the evidences of faith. We'll look at the answer to that question and the rest of our text. Lord willing, next Lord's day. All praise, honor, and glory for the riches of his glory. This mystery among the Gentiles which is Christ in you, the hope of glory. Amen. Amen. Let's pray together.


Winners focus on winning, losers focus on winners. So I don't need to look around the room for am I competing against Brad, am I competing? No, I'm gonna do what I do, I'm gonna stay in my lane and I'm gonna do it to the best of my ability and if I do that, it will be good enough to beat everybody else that's around me.


My name is Pranav Anamit and I'm joined with Jacob to talk about how users can deliver their modern apps anywhere, both publicly and privately. What we've seen as a most recent trend is developers are adopting new approaches in order to deliver their services faster. They've moved from the private data center to one public cloud, which is the hybrid cloud. But now there are actually users and developers are trying to adopt multiple public clouds as well as the edge so that they can deliver the apps or services faster by leveraging the best of each cloud. For example, maybe ML from Google or maybe some service from AWS or some service from Azure and try to leverage best of each service so that they can develop new services faster. Similarly, in the previous decade, users went from legacy apps and virtualized the apps into VMs. But now developers are adopting new application architectures such as microservices, containers and even serverless in order to develop and also deliver the new services faster. And the third big trend obviously was the move to agile and actually doing it and actually delivering the services faster. But now it has actually become continuous, it's basically continuous integration, continuous deployment, continuous delivery, as well as continuous verification of the application. So it's a constant iterative software development process. And all of this has been done by developers in order to deliver their services faster. However, delivering an app is not just developing the app. To actually deliver the app to the so that it can be consumed by a user involves multiple point of products and multiple teams. And these teams, they communicate using sort of support tickets. And because there are so many multiple point products, nearly seven of them, there's multiple iterations that you need to go through in order to deliver this app to this user. Each of these iterations takes days to weeks in order to get it right. And meanwhile, your app is not static, your app is continuously changing. The developer is because of the whole continuous integration, delivery, deployment and verification, the APIs are changing. So this whole process is continuously being iterative and taking longer as a result. And what is the end impact of this? The developer is developing the app faster. They are actually going fast. However, because they're going fast and because the current tools are point products are siloed, each of the individual teams, both DevOps and the network ops, network IT that also calls infrastructure and operations, they are actually getting overwhelmed and burdened because of this constant changes in the application. And this is negating all the efficiencies that the developer has gained by adopting a modern app approach. Let's look at why does it take so long to deliver the app? Let's look at firstly how long does it take? First, in order to deliver the app, you need to first obviously have some form of app management, which is either you can have your own Kubernetes cluster or your virtual machine, for example. So you have that. Then if you have a Kubernetes cluster, then you need an English controller so that you can direct traffic to this cluster from the outside. Once you have that, then you need an application firewall, an app firewall, which essentially protects your app-to-app traffic, products traffic coming into the application. Next, once you have that, then obviously you need to expose this app publicly.  So you need a load balance in front so that you can scale this horizontally. And this load balance is where you will basically terminate your SSL connection and you'll actually decrypt your traffic. So you need a load balance to do those functions. In front of load balancer, you want to protect that. You actually don't want it to be overwhelmed by malicious traffic. So therefore, you will add a network firewall so that you can block malicious traffic coming into the load balancer. Then in front of that, you need a router because you need the traffic to actually come in here. So you need a way to advertise the routes, the app reachability to the outside world.  So this is right here is your data center. In front of it, you actually need like a DDoS because you don't want to saturate the link between the user and your data center. So you need a DDoS to block malicious traffic coming in and only allow the good traffic. So you want the DDoS which is away from a data center, outside your data center, that is blocking malicious traffic and only allowing good traffic, ensuring that this link doesn't get saturated. So you need all of these different components before your app that you develop or develop can be exposed to the internet and allow users to talk to the app. Let's look at the time that it takes. This part, the creating a Kubernetes cluster and creating an English controller has become pretty fast mainly because of the whole infrastructure as code. There are these recipes available, charts available. So you can actually do that pretty fast. About two days for each, two to three days for each. So that is becoming quick. But when you start getting into all of these other components, the app delivery components such as an app firewall, that takes some time to actually tune the app firewall in order to reduce the false positive, to figure out what needs to be blocked. What do you turn on only the OS or do you turn on something else or what rules do you turn on? So that takes some time to tune. Then to figure out load balancer, to actually program the certificate, to actually create decision certification and to actually create a virtual IP and all of those take some time as well. It takes about one to two weeks. Same with the network firewall and the adultery. Each of these take about one to two weeks. And in the case of DDoS, because you're working with a component that is outside your data center, which is not modern in terms of having all of these click to turn it on and configure easily and quickly or doing it using code, it takes longer. It takes about two to three weeks to actually configure DDoS as well. So the total time that is taken by this app is to deliver the app is about seven to 12 weeks. And in this case, all we're doing is we're delivering the API publicly. Now, let's take an example of how long does it take to deliver the app privately, which means I have an app, I have an API and I only want either my partner app, which is sitting in another cloud to access it, or my partner customer or my business partner to access the app privately in their own data center. So say I have an app here in my private data center, I want this app to talk to another app which is sitting in the public cloud and I only want this app to talk to this app. I don't want this app to be or API to be exposed publicly on the internet. So in order to do that, all the other components remain the same. In addition, what you need to do is you need to actually have a private connectivity link between your private data center and your public cloud. In addition, you also need to have VPN so that these two can be in the same network and you also need to have this private link, which could be, for example, to disconnect or express route or essentially any private layer to connectivity between the two. So you could either do VPN over the internet, you could have a private link and then do a VPN on top of it, and there are multiple architectures. But all of this actually takes an additional three to four weeks. So to deliver an app or API privately, it takes about nine to 15 weeks. Now, if you look at this, why does it take so long to deliver an app? And is this right for a modern app? The developers sitting there going, I'm already, I'm gaining efficiency. I'm actually going faster. I'm actually adopting new architectures. But you're telling me that all of that efficiency is negated because of the existing mechanisms of delivering an app. What is the right approach that developers, DevOps, as well as network and IT and infrastructure and operations team should look for when your developer is going to use modern apps? We call that approach a distributed cloud approach. And the key differences between a distributed cloud approach and the current approach is what I'm describing in this slide. The first thing that you need when you are delivering modern apps is you cannot work with multiple point products. As I said, the application creation is a continuous process. Everyone's trying to move faster. If you have multiple point products and silos where you have to go one after the other, using support tickets to say, please issue me an IP address. Please open this port. Please configure the IP address. Please configure a rule, a network firewall rule for this IP address. Oh, by the way, my app died, came back up, and everything changed again. Please do a new IP address and so forth. It will not work in a modern app approach. So you cannot have multiple point products. You need essentially an integrated stack of these application delivery components which can move fast and namely in response to changes in the apps and the APIs because these are continuously changing. The second thing is the location of the app is no longer just one location, one data center. It's actually multiple locations. It is data center, a public cloud, a network cloud, maybe in the edge. So you need the same infrastructure components everywhere wherever you want to distribute your application. So the number of places where you need to manage these different infrastructure components is increasing. It's not just one. It's actually multiple. And therefore an appliance-based model where you're managing each appliance one by one with no longer scale is now you're talking about deploying multiple regions, multiple availability zones, multiple clouds, multiple places in the network, both the cloud network edge and in case of edge, multiple thousands of edges. So you cannot scale this using an appliance-based model. You need a distributed fleet operations model where your manager's entire thing is a fleet. Therein you are creating, you're defining your intent once, you define your intent once and saying this is how it should work and the system should take care of distributing the configuration to all these different locations where the application exists. So you need a distributed fleet operation approach. And to do that, the critical component which goes and said is you need a control-plane-based management. You need a control-plane to distribute the state, to distribute the reachability. You cannot rely on a management-plane approach of going one by one to every appliance. Third thing is once you've configured, how do you manage this? With seven different products? You have seven different port panes of glass where you need to go and see seven different things. You cannot troubleshoot a problem past because you have to go to seven different planes of glass. You need to also then go to, even if you take all of the metrics, the logs, put it all in a centralized system, there still isn't a way to thread the request together from one tool to the other. How do you thread a request or how do you uniquely create a single pattern of a request from the router all the way to your app? How do you know what is the key to in which you can uniquely join all these different tables? The fourth thing is the lifecycle management of it. The current tools are operationally complex because they're all appliance-based. That worked fine when you had one location, two locations. If you talk about multiple of locations, it's very hard to do lifecycle management of it manually. You need a full SaaS-based operations approach with full lifecycle management built in. It's fully managed and that's what you should look for. Lastly, if you want to scale to different locations, you cannot have the same form factor like a hardware or maybe a really thick machine that's in order to deploy it anywhere. You need something that is deployable in multiple thousands of clusters. That is what developers, DevOps, network infrastructure teams as well as the IT team should look for when they are considering app delivery for their modern applications. Let's look at, now that I've shown you what are the key tenets of a distributed cloud approach that the developers and DevOps and network of should look for, let's look at how it will work. How would you deliver a modern app publicly using this distributed cloud approach?  What you would first do is, first, you would essentially replace those components with a distributed cloud architecture. You replace or maybe you could do a new application using this distributed cloud approach. Now, getting rid of your existing infrastructure components, keeping an existing infrastructure components, this distributed cloud approach can essentially work over the top of that. You will first have that. The second thing is the distributed cloud approach should actually have its own network where you can advertise these applications publicly so that this becomes easier. The first thing that it should do is it should, essentially, you could have deployed your app anywhere. You could have deployed it in an existing Kubernetes cluster or your VM or so forth. It should discover what apps have already been deployed. Once it discovers this, it should have a control plane. Again, this control plane is critical. This control plane is essentially advertising application reachability. It's not describing routing. It's not just describing the layer three routing. It's describing application layer reachability that says to reach API one, not IP address one, but API one, here's how you reach this API. And then it also distributes app health. You need to distribute that. Once you have used a control plane, the next thing is you need to then advertise the app. So you should advertise the app publicly. In this case, we're advertising the app publicly. So the distributed cloud approach should enable the user to actually advertise, to choose where you want to advertise the app. In this case, we're advertising the app on, for example, a public pop using an any-curse virtual IP. This will direct the traffic from the users onto here. Then the fourth thing using a distributed cloud approach is you should then have the ability to distribute app delivery functions closer to where the data is generated or to where the user is. In this case, for example, we should have the ability to distribute, for example, SSL offload closer to the user. This way, you're improving the application performance. The second thing is you should have the ability to distribute a web application firewall functions closer to the user. This way, you're actually protecting your applications further away from your data centers. You're protecting it right here. And all the malicious traffic is blocked right here, rather than having a backhaul to your data center and being blocked in your data center. So you should have the ability to distribute your different application delivery components closer to where the data is generated or where the user is. And then lastly, in order to make sure your performance is good, you should have a persistent connection between from the front end all the way to your origin. So you're not doing multiple TLS setups for your application. This is how you would deliver an app publicly using a distributed cloud approach. Let's take the same example of delivering an app, in this case, privately from one side to another side, using the distributed cloud approach. Again here, we are saying keep your existing app delivery components. Keep it as it is. Don't get rid of it. But you deploy a distributed cloud application gateway over here. And then this application gateway, as I said, first, it should deliver. It should discover what apps are configured. Second thing is you need to have a global, you need to have private connectivity. You should look for solutions that essentially incorporate private connectivity to all different components, both your private cloud and your public cloud. So you can have private links with each of these so that you don't have to set it up yourself. The service comes, the solution comes with that. And all you're doing here is you're discovering your app. In your control plane, you're now advertising the app reachability to the site where you want the app to be consumed from. In this case, you want to do consume from this site. And then here is where you advertise the app privately to that site. So this app now is reachable only from this site. So this is done using policy. It's not reachable from the internet. So you cannot have traffic coming in from here. This will not be allowed or should not be allowed by any solution that is offering this. This app should only be reachable from this location. And now you can choose to distribute your app delivery functions closer to where the traffic is being generated. In this case, you can distribute maybe SSL termination or web application firewall right here. So that all traffic malicious traffic is blocked over here and it's not backhauled to this site. And then lastly, because this is a completely private connection, this is not going over the internet. This essentially reduces your risk profile of the traffic. So this is completely led to connection. You're not exposed to the vagaries of the internet, such as congestion and so forth. Now, let's take a look at what is the benefit of using this distributed cloud approach? What is the impact on the different teams? If you see the distributed cloud approach and actually Yaku will show you how long it takes, we're going from order of weeks to order of minutes and hours essentially, right? So it's a significant improvement in terms of the time taken. What that means for DevOps is that now they can actually deliver new services faster. They can actually keep up with what the developer is doing. And so instead of the app delivery taking, say, three months, four months, which means in a given year, you can only do like three or four services, you now can actually deliver new services almost every week or every two weeks, right? So you can actually deliver new services faster. So you can go from three to 11, which means now you're basically bringing in more top-line revenue to the organization, right? The second benefit is that with the different locations such as private cloud, public cloud, and so forth, you need to have different teams to manage each of these different locations. So in this case, this customer who went through this, they actually had a team of 25 with almost 15 QA and 10 DevOps to manage these different locations and to manage these different point products. But now by using just one product and in different locations, they can significantly reduce their operational team from about 25 down to 25, which saved them a significant amount of money as well. And the third component of this is that troubleshooting problems. This is like day three, since you had to go to 300, since you had to go to multiple portals, it took about five to six hours to troubleshoot every incident. By using a single pane of glass and a single distributed cloud approach, they can reduce the operational time or the troubleshooting time from 300 minutes down to 15 minutes per incident. And this saves a significant amount of time so that they can focus less on troubleshooting problems and more on delivering new services and more on the top line, focus on the more high value items rather than focusing on infrastructure level components that do not add business value to their company. So this is the business impact of going with a distributed cloud approach compared to the existing multiple point product siloed approach. So I've spoken a lot about this in the slides, but I'll hand it over to Jakob that he can talk about. He can show you some of the distributed cloud approaches and how easy it would be to actually configure using this approach. Okay, let me share my screen. Okay, can you hear me and see the slide? Yes. Okay, so now I prepared a short demonstration of Pranav explain. So you want to show you also some real stuff and how hard it is to do it or how easy and how it looks. So basically I decided that I will pick simple app. I didn't want to do complex microservice for this demonstration so I took like common application in this case which is WordPress and MySQL and what I have in my demo setup is Vanilla Kubernetes cluster running in virtual machine in private data center and I think I'm using Calico as a C9 plugin. So really Vanilla Vanilla topology and two pods, one WordPress, one MySQL. And to do this action in a normal world as Pranav explained and I have very good experience with this, that usually this part is handled by DevOps people and people like me which is pretty doable and it can be pretty fast so you set up VM with Kubernetes, you deploy Enginix ingress controller, you will use the Let's Encrypt threat manager which will give you automatically certificates, you can do all this stuff but then my issue always was the left side where if you are in big company you need to create a support ticket for the network team and then it takes if you are lucky it takes three days but it can also take two weeks to set up the firewall and all this stuff here and it is not very flexible and also hard to debug I will also show this so to map it what you will see in my demo is I will basically will not need left side, I will focus here and I will have my Vanilla WordPress because most of the people today they already have Kubernetes running and they want to expose DDoS protection for their site and they want to use web application firewall and they want to have a central visibility through one console so that is my goal in this demo so what you will see so here I have a private data center and this is a Volterra global backbone with few global pops and distributed anycast where I am going to advertise the site and here is the end user so as a first step I will discover the app so in my other virtual machine I decided that I will run Voltmesh as a virtual machine you can run it as a pot in the Kubernetes as well but you in this case I'm running it in the separated virtual machine I will load the kube config it will auto discover all the services in this cluster then because I have a distributed control plane I can immediately have a reachability anywhere and I can expose an application locally globally in different data center very easily you will see it and I'm getting all this for free now next step I will advertise it on anycast so it will be accessible from the closest routable point and then I will configure SSL offloading and web application firewall and we can do rate limiting or service policies for specific ASN so there are multiple combinations what we can do and then the user will access this and he will end up in my private DC on the WordPress so now let's let's go ahead and start so this is my terminal and I really have just single node vm and if we take a look I am using Calico as a CNI plugin so it's really like most popular plugin what people use so nothing special very simple setup and in default namespace I deployed WordPress and my SQL and I'm using I created services service for the WordPress now let's take a look how we will configure the volt mesh through console so this is a volt console which brings the central view I am based in Prague so I deployed volt mesh virtual machine in the DC Prague site and I have a visibility so I see the the health and basic information about this about this node I can go inside and see how much how much traffic is going through this through this node so this is like a system view I can see a number of nodes so it's a single node vm I can read the IP address utilization metrics from CPU memory so this is like a overview in in our console we call it site and my site is DC Prague now to start with the first step I need to discover WordPress service and all services which are there so I go to service discovery section and in service discovery we will create a new config for DC Prague and we need to say where where my where I want to discover we have concept of virtual site if you would like to discover from multiple sites by single config or I can choose the site in this case I will say I want to discover on my Prague DC Prague and I want to discover on local network so basically the there is a local connectivity between the volt mesh node and Kubernetes cluster now today we support console and Kubernetes I'm using Kubernetes so I keep Kubernetes I do configure and now it is asking me to provide a kube config kube config I can I can either give a plain text clear secret or we have mechanism how to encrypt the secret so it can be decrypt only in the target location and it cannot be decrypted centrally in this case I will go with clear secret and we need the kube config so this is my kube config right with the private IP where I am sitting so I will just copy kube config and I will paste it here one more option what I what I can choose is if I have a port isolated or if they are reachable so in case of calico uh since volt mesh support bgp peering I could even do the bgp peering between uh calico route reflectors and and my volt mesh but since I did really basic calico deployment it is using some vxlan encapsulation and I cannot reach the bots so I keep bots are isolated it means that it will use a node port for the service then I could configure some other stuff like publishing web services but this is not the for our studio demo so I can just save it and if I refresh you can see it discovered four services and one of the service is uh wordpress default which is matching exactly what what we saw in my terminal you can see right so this is the uh this is the service and it is this is the same so now I discovered the endpoint and it's time to go and um create uh http little balancer uh before I create http little balancer uh I have to configure the origin pool because uh wordpress requires special route config to to be able to work so I will go and create origin pool which is basically saying where my uh wordpress is running where is it served so we can go and say uh wordpress and it will be kubernetes service it will be wordpress default site is sprag uh I am discovering it on uh outside network and port port is 8080 I can create health checks I can create tls in this case I'm using in sikur on the kubernetes so we can um the services export on port 80 so I will keep it as is now um wordpress requires um uh route host drive right to be able to work so what I did before this demo this is really wordpress specific I created the the uh the route object where I will just now add the at the origin pool so that should be uh easy to do okay and it's uh it's actually there so we don't need to do anything now uh let's create the sttpl balancer so to create sttpl balancer uh we can say wordpress and domain so for domain I decided I will use uh delegated domains so what it means uh in the system namespace we have ability to delegate so this is my domain which I own up vk.tls I own and uh you can delegate it to us and then we automatically provide let's encrypt certificates and we manage the ns records it's an optional thing so so before I had to create this ns record and delegate my domain so now I can create any any sttpl balancer and automatically I get certificates from let's encrypt and everything so the way how it is configured is uh I can say here if I want automatic certificates then it will use the delegate domains or I can bring my own certificate in case that I have my own I can use this and upload the key and cert I will use automatic and the domain domain will be uh wordpress.app vk.tls I own now I want to have HTTP to uh HTTP redirect to HTTPS and I will use my route config which we configured so for the route config I will just choose the object what what I had there and now the almost the last point is where I want to advertise the configuration so in this case we want to advertise it on the internet so it will be globally available but we have other options like you can advertise it locally in the cluster or in the different specific location in this case it will be internet and then what we want to also do is we want to configure the WAF so to configure WAF I can actually I have two options either I know exactly what I want and I am someone who understands web application firewall very well so I will define my own rules and reference the rules or I will do the WAF intent in this case I want to show you the WAF intent and the way how I will do it is I will create new WAF wordpress and I can just simply choose PHP and wordpress and it will automatically pre-configure the right profile for me the right application profile what I want and this is important I can say do I want to block attack when it is detected or I can raise the alert I will demonstrate the attack so let's do the block and you will see how it blocks my attack when we will try it from the laptop so this is the WAF configuration and that's it I think now we can just save it and what will happen is that it will start the DNS domain verification and in a few few minutes we should have our our load balancer ready and we can actually try it so the domain challenge verified and in in a few seconds it should be there certificate valid so the vhost is ready this is my domain and we can actually try yes and this is my wordpress site so you see how quick it was it and I have valid certificate I have even redirect I should have right should redirect me so you can you can all try let me let me see what is the chat window so I'm going to send it to everyone so you can guys open in chat and you can try to open the site and we will we will see the some traffic so now what I can do is I can start generating some traffic so it will be it will be visible there that we are that someone is coming to the site okay so I'm generating the traffic to the sites site is running and this is what I've just shown you is how hard is to do configuration so it really took like 15 minutes including explanation and we have configured easily wordpress which is running somewhere in in the private data center without direct public IP or anything it's just sitting somewhere on the internet connection and that's that's all what is needed now we can go back and we can take a look on troubleshooting part and the visibility this is important again if if if I sorry this is this is my google home assistant he got crazy he started playing some music okay so in normal world it is very hard to troubleshoot right and some and I have a good experience that even to get the latency between all these places very stuck or the locks you really need to build the solid monitoring and logging where you will send all those locks and you will have very good visibility and it takes time to build it and sometimes hard problems troubleshooting of hard problems can take even three hours to figure out where the actual problem is right if it is on firewall because something some IP address is blocked there or it is in the WAF right just tune WAF for your rules is a sometimes complicated exercise to to find the right rules and it can take days to even weeks to tune all the values think especially when you have some custom application so all this is very hard to do and I'm not saying that with this it's easy it is also hard but you have everything in central places so it's not about that you don't need to do troubleshooting and this just magically work always no but you have a single page where you can see all the locks all the metrics latency between locations and all this information are there you can integrate notif do integration with the notifications to your external systems you can send locks to your Splunk or or Datadoc so we have all these integrations and it is much faster to debug such a problem to show you what I mean is let's do the quick overview so you see both data we are getting and how how looks the visibility part so you saw the config part now we can actually take a look on the application traffic and on the application traffic we can see that now from the public network traffic is flowing looks like people started opening the site because it's really flowing from Singapore, San Jose, London, Amsterdam and Paris so this is all our pops and then it goes to DC Prague so we see that literally from all the places it is coming right now so this is like a application traffic visibility now I'm going to go inside the HTTP local answer itself and I can go on WordPress now and what we see here this is pretty nice because the average latency between client and our global backbone load balancer is 25 millisecond but then it takes 140 milliseconds to reach actual virtual machine running in the DC and then less than one millisecond to go to the application so this is like total upstream so you can see here we see that we have total 14 unique visitors in the last five minutes I can see which operation system they are using top clients right so top is Paris this is probably my watch my generator I'm reaching Paris browser type TLS top ASN right so I have all this information now I can read the metrics so I can see the request rate and right now it's a one request per second in last hour because we just launched it I can see the traffic so majority traffic goes to Paris and San Jose now the interesting part is the is the request so here I'm getting sampled request rate and I can filter by code I can filter it by country by ASN top source IP so this is my IP fingerprints right and let's take a look on some US requests which are coming and you should be able to see so here is one of the client IP and we can take a look we see the latency for this particular client and duration type of OS and also we should see the country which instance it reach right ASN and city right so this is the basic info what I am getting from every every request very easily I can filter out 405 and keep just 200 right and easily I can navigate and see all the requests which which are coming now we have a more features like api endpoints like machine learning but that would have to run for more than one hour to get some to learn some stuff and display it but now let's take a look on the on the application firewall and security events so what I'm going to do now is I'm going to generate attack or attack so WordPress has some open source tool called WordPress scan and you can run it and it can tell you what version is there what is available to do and potentially you can try to hack the system so let's see right so I will run basic enumerate and you can see that the basic just the basic one immediately got aborted with 403 and it's saying this is might be due off so basically our buff is blocking the traffic so we don't see it so we can try to send a random user agent and now this will go through it will not discover much but we should actually see the attempt to dump SQL and try some basic WordPress URL which usually people trying to hack and attack and we should see the alerts immediately and it should be blocked so let's let's let's take a look so if we if we refresh it let's put the last one hour and in a few seconds we should start seeing the alerts see so now actually this is me right so there is already a security event so we can see the security event which which happened just now and you can see that buff mode block it it hit two counts right and this is the rule ID which was hit so this rule ID is sometimes also used when you want to disable some rule IDs because it's you are getting false positive blocks so then you can you immediately see which rule ID blocked your access and you have information on what that it was actually a WordPress scan agent who who tried to scan the site if we refresh we should see the more alerts coming from the second run right so this was this was uh this was other run when it was trying to do dump SQL on on the upload so I immediately see it and in the upfire wall you see that last five security events they are coming here and you can actually filter it out and easily see what is happening so this is a simple example where I just show you how in a little 15 minutes set up like globally distributed application running in your DC with laf and dedos protection and very easy to do so now I'm going to pass it back to Pranav for the final slide yeah so um I think we can open it up for questions since we are almost at the top of the hour I can open it up for questions if any questions that you may have and as a reminder you can just add your questions to the q&a box at the bottom of the screen and we do have about three minutes left yeah so there was one question that was interesting um the I think the question was uh do apps need to be modified in order to use this and uh I think let me just answer for the benefit very well the apps don't need to be modified at all right the apps are what you want to develop you can tell the apps in any language and you could be anywhere containers vms anywhere what we do as I said is we discover the app and you discover the app using either dns based mechanisms using using the kubernetes discovery using uh using console discovery different discovery mechanisms and you discover the app and once you discover the app then your art control is then taking the app and advertising the reachability of the app over to different locations both public as well as private and then any changes to our control to the control plane the control plan is essentially control plan so that doesn't affect your app the developer doesn't have to change the app in order to account for just a little I think that was the one question nice so um anything else yeah there were no other questions that I could see in the chat um uh is there is any other question um is there any other question uh that was answered uh that was asked earlier um just um let's see here what is the advantage of distributing load balancing and ssl termination to the network edge yeah one of the uh one of the big advantages um that of distributing uh application delivery functions uh to the network edge is that firstly these functions take up our performance are compute intensive so they take up a lot of cpu cycles such as uh ssl termination decrypting the ssl traffic takes up a lot of cpu cycles so distributing it out away from a data center conserves cpu cycles on your data center on your public cloud so that's one so reduces your cost but the more important thing is by distributing the application uh delivery function closer to where the user is actually improves application performance because to set up a secure connection from the client to the actual app to the server uh is a is like a six message dance and doing that over long distances where the latency is high actually reduces performance so if you do that set up closer to where the application is and then you have a persistent connection from the network edge to the uh origin server this way your performance all your chattiness is is you know in country for example and then the over the long haul you're not you're not doing this constant um uh a handshake which actually improves application performance so distributing application functions are waived and closer to the user improves application performance uh reduces the uh risk uh because all of the attacks are blocked to the edge and uh reduces your cost okay thank you pranav um we unfortunately have to wrap it up now any closing closing comments uh no thank you for ever joining uh if you have any questions feel free to reach out to uh to uh to yakubo myself uh we are on twitter on linkedin on um on on email and we are happy to answer any of your questions so this is this is our hand rules uh feel free to reach out and we can answer any questions offline too wonderful all right thanks so much everyone and enjoy the rest of your day bye bye thank you bye bye