Bhuvnesh Anand

okay in sql injection we use prepared statements prepared statements are nothing but the statements which separate the data from the sql query so during sql attacks happens when a user enters malicious javascript code into the system which will access the confidential information in the system and the data from the database so in order to overcome this we use prepared statements also we what we do is we will validate the query we will validate the inputs before sending them and we remove access we also avoid

Could you let me understand more about your background by giving brief introduction of you? Okay. Myself, Bhuvanesh Anand, I've been working for 8.4 years in Morphine Server. I have experience in PHP frameworks like Core Igniter and Laravel, and back-end technologies like MySQL, CorePHP, and front-end technologies like Bootstrap, jQuery, JavaScript. Recently, I also worked in React.js projects. The main responsibility given in that company is taking care of management portal. The portal had 35-plus modules like IT management, HR management, admin, sales, almost 100 to 150-plus users use the system. This system is handled by myself. Every day, I used to get the feature updates, maintain the system, always take the user's suggestions to make the user interface compassionable and easy to use. It was a wonderful experience working with Morphine.

Okay, in PHP, the main principles we follow is, first we design the architecture like a model, view, controller. Models take care of the connection with the database. Controllers take care of the business logic between the view and the model. And view is the presentation layer. We always try to segregate the database interaction and the view by using controller logic. This helps to keep the code maintainable. The user, we use form validation so that valid user inputs get into the system. We also escape the characters which might not be well structured, or which can easily break the system logic while displaying.

What are the steps you take to mitigate a cross-site scripting vulnerability following WordPress theme you developed? So cross-site scripting mainly occurs when a user tries to access the data which is inside the database. So when a user is entering the data through forms, we need to validate the proper data entering into the system. We can use form validations. And there may be possible of excess threads that may not hold good for the system's data.

Can you identify potential SQL injection points in the WordPress website? For more information, visit www.sqlfinancial.com

What methods do you use to test and verify the security? So if the data, suppose if we are fetching the records which is more than 1 lakh count then probably there may be chances that the load is more and the records may not display as expected. So what we do is we can use, we can catch the data, if suppose in case if multiple pages are accessing the same data we can use catch, PHP catching techniques in order to overcome the load. We can use pagination to load only the required data and if it comes to security we need to make sure, we need to authorize the data by checking if the user is logged in. Only authenticated users has to be allowed to check the, allow the data.

Okay.

How do you ensure that the PHP function you develop follows the single responsibility?

I will remove the filler words and correct the grammatical errors. Here is the corrected text: To handle error logging and exception handling in PHP, the first way is to write test cases and use return statements to check whether the data we are getting is as expected. We use try-catch blocks to check the code, which is one of the methods we can use to check error handling and use try-catch to check the code.

What approach would you take to optimize MySQL query? I can use explain statement to understand the query. I can use I will check whether how long whether there is repetition in the SQL queries. I will always avoid queries which if you if you are selecting the all columns and for example select star is not is avoided is avoided and only use only the where classes wherever it is required.