Please note that JavaScript and style sheet are used in this website,
Due to unadaptability of the style sheet with the browser used in your computer, pages may not look as original.
Even in such a case, however, the contents can be used safely.

End of menu.

Main contents start here

Need of SiteShell

1.Why Web application security is required?

Web applications are prone to several types of attacks including SQL injection and Cross Site Scripting. Since a network firewall considers these attacks as valid accesses, they cannot protect Web applications.

Why Web application security is required?

2.What are the countermeasures for Web application vulnerabilities?

1.Modify the application (Yr 2000 onwards)

Web application source codes are studied for incorporating the necessary measures.

2.Whitelist type Web application firewall (Yr 2005 onwards)

A list containing the data to be allowed by WAF is defined, and data not present in the list is blocked. This method is mostly adopted in hardware type WAF.

3.Blacklist type Web application firewall (Yr 2008 onwards)

Data matching with data patterns (Signatures) defined in blacklist is blocked or rendered harmless. This method is adopted in software WAF.

3.SiteShell is very helpful particularly in such scenario!

Do you also find following types of problems? If yes, Siteshell is the answer.

Case1：You have got your website scanned for vulnerabilities; however, don’t know how to take measures.
Case2：Unable to perform source code modification.
Case3：Surprised to know that there are attacks that cannot be prevented by firewall and IDS/IPS.
Case4：Recently, there is much talk about WAF, but you think it is costly.

Top of this page

End of this page.