"Hey Dude, I've just hacked your site"

How would you like to hear someone say that after crashing your site? And what would your answer be? PortalKeeper : the first complete firewall for DotNetNuke apps.

Why a firewall for DNN? Because just like you, we have clients who have critical data on their sites and require a 24-7 service. And in case of an attack, patches from Microsoft will always come too late.

What's the scope? A rule-based application analyzes every entering request on your site. A bunch of boolean expressions will filter them and do nothing in 99% of the cases. But when an anomaly is matched, PortalKeeper module takes immediate action: reject the request, redirect to an error page, send an alert to admins, log an event, disconnect the user... Whatever protects your portal efficiently.

Why should I care? Because unless your network is down, you can be attacked. Because hackers love Microsoft platforms. Because you did a great job building DNN sites and don't want them down. Because no other module provides such extensive protection. Because there might be another security breach tomorrow. And because your clients deserve the best service.

How much does it cost? Not a penny if you get the FREE version (coming soon) which will guaranty minimal protection against Denial of Service, Multiple connexions, cross site scripting... For custom protection on critical portals, you should get the STANDARD $100 licence here.

What am I waiting for? Good question, Dude...

Buy Me!

Features

Look & Feel

Engine rules

A rule is made of conditions that trigger various actions when matched.
Default rules provided:

1. Denial of Service protection (DoS)
2. Critical accounts protection against social engineering attacks
3. Warning email in case of simultaneous connections from the same user
4. Super User backdoor
5. Geographically Limited registration
6. Warning message for IE6 users
7. Etc...

Example: Hide login button so that unauthorized IP addresses cannot log in

Conditions

These elements define the conditions to be matched by the client request to trigger the rule.
Conditions are boolean operations which depend on:

1. Client source condition based on 5 types of sources:
   1. Country
   2. IP address
   3. Session
   4. Path to the page
   5. URL
2. Portal alias condition
3. Membership condition
4. Request Caps condition
5. Multiple connection
6. Dynamic expression

You can create your own condition providers

Actions

These elements define the actions to be performed when above condition is matched.

1. Multiple Action
2. Log Off
3. Redirect
4. Request Denial
5. Log Event
6. Auto Login
7. Customize Environment

You can create your own action providers

Error customization

Recovery string