Notice Board

PatTakhaZOne Web Serf Education Purpose keh lhya ha. Jasa keh ap janty hein keh Takreeban 100% ma sa 90% patches, Craking tools or Hacking software mein virus hota ha.PatTakhaZOne peh har ek tool check kiya gya oR Trusted ha :) Ma Kud ek ek sofware Ko check Krka upload krta hon. Umeed ha apko meri posts pasand ahy gi.(Every SOftware is 100% Secure and Trusted) All information on this Blog is for educational purposes only.

Showing posts with label How to secure your website. Show all posts
Showing posts with label How to secure your website. Show all posts

Use your Chrome Browser as Notepad quickly

Rehan Ahmed  , ,  

Use your Chrome Browser as Notepad quickly.





Just copy the text below to the address Bar.
data:text/html, <html contenteditable>
Note: You can also bookmark this to use it anytime

Read More

How To Secure Website With HTTPS

Rehan Ahmed    

How to Tell if a Website is Secure



Pages that don't display a lock symbol in the web browser but are https (not http, but https - the "s" is the secure port, 443 instead of the standard port, 80) could still be secure but that's not the best practice in website design - let's explain...

What many people may not understand is that the page you're putting your credit card information into does not need to be secure itself. It's just a form on a page that where you put your information into. For you to first get that page containing that form, the connection did not need to be secure. However, the page that the information is being submitted TO does have to be https for the transaction to be transmitted securely to the server. Let's take a step back for a moment...


Forms (like credit card forms on a page) have two parts:



The page the form is sitting on.
The script (and page) the form submits to.
We call the submit (clicking the "check out" button or whatever) a "post" in web lingo - the form posts to a script (computer program) sitting on your website. This is a PHP or CGI or DotNet program that does something with the information it's receiving. When you post the form to that script, that communication does need to be secure. That is what makes a transaction secure - well, part of it.

The next part of the secure transaction happens within the script itself. That script can either store the information (which it really shouldn't if it's sensitive information like a credit card or social security number) or else it does something else with it like send it through a payment gateway and subsequently from there, the paymet gateway connects with a bank to see if funds are available, for example. The communication from the script (server) to the payment gateway also needs to be secure. There's no way to tell in your web browser if that communication is secure since it's beyond your web browser - another layer deep. You just have to trust that things are set up right and that's where there's such a thing as PCI Compliance.

Best Practices



With that said, people ARE used to seeing the lock symbol on the page that they are putting their information into. If that is done, then you, as the website owner, are showing your customers that you value their security and sensitive information and are conyeing to them that you have adequate security in place. Having a lock in the address bar is the best practice and should be followed.

Problems



The problem that is most likely encountered when a page with a credit card form on it does not have the lock symbol is that there is an element or two on the page that was not transmitted to the website visitor securely. This item can be anything from a JavaScript file to a CSS file (stylesheet) to an image or video. Our clients will often add some sort of widget or code they get from another website to their website template and since that code has references that are http and not https, those elements end up on https page, casing the web browser to not show the lock symbol.

To fix it, those items must be removed from pages that are secure - meaning pages that have https in the address bar. Often, we need to write some logic into the template/theme file to not show some particular code on a page if the page is secure. Another fix is to change the URLs to https but if the server hosting that piece of code does not have an SSL certificate installed, then it cannot be done.

Another thing that can wrong is that the SSL certificate is expired. If that's the case, then the website visitor will see a warning stating that the transaction might not be secure. Make sure you know when your SSL certificate is set to expire so that it can be renewed before it expires - this way, people will not see this message.

What if This Happens?
Here is what you should do:



Webstix Clients - If you notice a lock symbol not appearing on a website we've built on a page that should show it, then please contact us so that we can investigate it and fix it right away.
Non-Webstix Clients - If you're not a Webstix client but still want a page that is not showing a lock symbol fixed, then please contact our Website Maintenance Department, submit a ticket to us and we can get you a quote on that work.
Website Visitors - If you notice the absence of a lock symbol on a page and you ended up on here, looking for answers, then please contact the owner of that particular website and make sure they know that their secure pages are missing the lock symbol. Again, those pages should show "https" and not "http" in the address bar (some web browsers are not showing the "http" part anymore, we know. There are ways of turning that back on.

Read More

How To Secure Your Website Using .htaccess File

Rehan Ahmed    

In this article, I will teach you guys on how you could secure your websites in just one minute.
Simply create a file named as .htaccess and paste the following code below:

Script: htaccess Security By PATTAKHA MUNDA


                                                

# No web server version and indexes
ServerSignature Off
Options -Indexes


# Enable rewrite engine
RewriteEngine On


# Block suspicious request methods
RewriteCond %{REQUEST_METHOD} ^(HEAD|TRACE|DELETE|TRACK|DEBUG) [NC]
RewriteRule ^(.*)$ - [F,L]


# Block WP timthumb hack
RewriteCond %{REQUEST_URI} (timthumb\.php|phpthumb\.php|thumb\.php|thumbs\.php) [NC]
RewriteRule . - [S=1]




# Block suspicious user agents and requests
RewriteCond %{HTTP_USER_AGENT} (libwww-perl|wget|python|nikto|curl|scan|java|winhttp|clshttp|loader) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} (<|>|'|-|%0A|%0D|%27|%3C|%3E|) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} (;|<|>|'|-|"|\)|\(|%0A|%0D|%22|%27|%28|%3C|%3E|).*(libwww-perl|wget|python|nikto|curl|scan|java|winhttp|HTTrack|clshttp|archiver|loader|email|harvest|extract|grab|miner) [NC,OR]
RewriteCond %{THE_REQUEST} \?\ HTTP/ [NC,OR]
RewriteCond %{THE_REQUEST} \/\*\ HTTP/ [NC,OR]
RewriteCond %{THE_REQUEST} etc/passwd [NC,OR]
RewriteCond %{THE_REQUEST} cgi-bin [NC,OR]
RewriteCond %{THE_REQUEST} (%0A|%0D) [NC,OR]


# Block MySQL injections, RFI, base64, etc.
RewriteCond %{QUERY_STRING} [a-zA-Z0-9_]=http:// [OR]
RewriteCond %{QUERY_STRING} [a-zA-Z0-9_]=(\.\.//?)+ [OR]
RewriteCond %{QUERY_STRING} [a-zA-Z0-9_]=/([a-z0-9_.]//?)+ [NC,OR]
RewriteCond %{QUERY_STRING} \=PHP[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12} [NC,OR]
RewriteCond %{QUERY_STRING} (\.\./|\.\.) [OR]
RewriteCond %{QUERY_STRING} ftp\: [NC,OR]
RewriteCond %{QUERY_STRING} http\: [NC,OR]
RewriteCond %{QUERY_STRING} https\: [NC,OR]
RewriteCond %{QUERY_STRING} \=\|w\| [NC,OR]
RewriteCond %{QUERY_STRING} ^(.*)/self/(.*)$ [NC,OR]
RewriteCond %{QUERY_STRING} ^(.*)cPath=http://(.*)$ [NC,OR]
RewriteCond %{QUERY_STRING} (\<|%3C).*script.*(\>|%3E) [NC,OR]
RewriteCond %{QUERY_STRING} (<|%3C)([^s]*s)+cript.*(>|%3E) [NC,OR]
RewriteCond %{QUERY_STRING} (\<|%3C).*iframe.*(\>|%3E) [NC,OR]
RewriteCond %{QUERY_STRING} (<|%3C)([^i]*i)+frame.*(>|%3E) [NC,OR]
RewriteCond %{QUERY_STRING} base64_encode.*\(.*\) [NC,OR]
RewriteCond %{QUERY_STRING} base64_(en|de)code[^(]*\([^)]*\) [NC,OR]
RewriteCond %{QUERY_STRING} GLOBALS(=|\[|\%[0-9A-Z]{0,2}) [OR]
RewriteCond %{QUERY_STRING} _REQUEST(=|\[|\%[0-9A-Z]{0,2}) [OR]
RewriteCond %{QUERY_STRING} ^.*(\[|\]|\(|\)|<|>).* [NC,OR]
RewriteCond %{QUERY_STRING} (NULL|OUTFILE|LOAD_FILE) [OR]
RewriteCond %{QUERY_STRING} (\./|\../|\.../)+(motd|etc|bin) [NC,OR]
RewriteCond %{QUERY_STRING} (localhost|loopback|127\.0\.0\.1) [NC,OR]
RewriteCond %{QUERY_STRING} (<|>|'|%0A|%0D|%27|%3C|%3E||-) [NC,OR]
RewriteCond %{QUERY_STRING} concat[^\(]*\( [NC,OR]
RewriteCond %{QUERY_STRING} union([^s]*s)+elect [NC,OR]
RewriteCond %{QUERY_STRING} union([^a]*a)+ll([^s]*s)+elect [NC,OR]
RewriteCond %{QUERY_STRING} (;|<|>|'|-|"|\)|%0A|%0D|%22|%27|%3C|%3E|).*(/\*|union|select|insert|drop|delete|update|cast|create|char|convert|alter|declare|order|script|set|md5|benchmark|encode) [NC,OR]
RewriteCond %{QUERY_STRING} (sp_executesql) [NC]
RewriteRule ^(.*)$ - [F,L]

Just Save it and if any Que . Please Don't forget to comment below on this post. Thanks

Read More
Subscribe to: Posts (Atom)

 

Copyright © 2015 Only For Education Purpose.