AD-002: RBL Submit for clearance tool

Summary: We need a web app which can submit IP addresses to web based forms for the purpose of clearing black list entries from abusive hosting clients (spammers, hackers, etc). Our clients are data centers who have large numbers of these type of listings to clear each month but unfortunately most of the lists use web based forms allowing 1 IP to be submitted at a time and often use some form of captcha security. logins, etc. We're looking for programmers who can come up with solutions for us to be able to automate this process such as automatic captcha entry or at least make it easy for a human to enter these rapidly, etc.

Project Details:

Workflow -

1. Import IP addresses from a database where client profiles and IP address allocations are stored.

2. Retrieve the current listings for the IPs from another custom applications database

3. Create a processing list of the actions needed to clear the listings from the IPs. These actions are pre-defined according to the list involved and type of listing. The actions will include:

A. Making the IP address idle (not allocated to anyone) and Clear any RDNS entries (send req email to datacenter)

B. Set number of "idle" days specific to the listings, schedule a re-check of the listings after "idle days" has passed.

(Some low level listings will drop off automatically if the activity in question stops for "x" number of days, usually 1 to 7. For these we will want to make sure the IPs are not being used, have no RDNS assigned and then let them sit idle the required number of days. After this, we need to check the listings database again to make sure it worked)

C. Submit IPs for de-listing. (If a listing requires a request to delist be made, the action list should display each RBL the IPs are on which will require this).

4. Process Workflow - user triggered button which will process the workflow listed above. Completion of process steps should be indicated on the UI as should any failures of the system.

5. Results Screen - This should indicate if process completed or did not complete and present an error code for any failures. Failed process steps should show an option to repeat the process workflow again or send the task to a manual processing queue.

6. Manual Processing - For any tasks which could not complete due to errors after retry or have to be performed manually, this queue should show the Client and the client's IPs / Ranges to be processed. Drilling down to the client should present a list of ranges, drilling into ranges should show each IP. Nex to each IP should be the manual process required (such as submit IP for delisting) with a link to the submission page. If an account login is required the app should either handle the login automatically or at least present the user with the account login info. Once the manual submission is completed, the user will check off that it was done which will switch each IP to indicate that task was completed in the workflow.

----------------------------------------------

Back End Components:

1. Database of client data:

1. (company, email, contact person, etc)

2. IP ranges to be processed. These ranges could be listed as CIDR format (/24 - /20 - etc) or could be start ip-end ip (192.168.1.1-2 or 192.168.1.1-192.168.1.2)

3. IP Status (clean or listed and severity)

4. Monitoring ? (Clients with this option have their ranges monitored continuously and cleaned as needed)

Database of RBLs:

1. RBL title and description

2. Severity level

3. De-listing method (web form, idle-24, idle-7, re-test, email)

4. URL of web form and any configuration details needed to automate submissions

5. Contact Email for RBLs requiring request via email

6. Notes (details for our users on best way to deal with RBL staff, etc)

Admin UI:

1. Create User accounts and assign roles for this app (roles are user or admin, only admins can perform this function)

2. Create and edit client profiles

3. Create and edit RBL database entries

4. Assign Work (client to user)

AJAX MySQL PHP Shell Script

Nº del proyecto: #1318164

Sobre el proyecto