Administrative and Maintenance Tools - [DBTech] vBSecurity v2 (vB4)

vBSecurity: What is it?
vBSecurity keeps a watchful eye over your forum even when you are not there, and has the capability to alert you of any suspicious activity.

Uses

vBSecurity is the ideal product for forums that are concerned about security, or wish to be alerted when something suspicious happens.
It keeps a watchful eye on your configuration file, ensuring that it does not get modified by mods or plugins.
Another important feature is the ability to add a secondary login, unique to each administrator, that is required before accessing the AdminCP. Ideal for forums where multiple administrators may share login information, or where administrators may log in from public computers.
Add in quick settings for the most vital vBulletin Options and Usergroup password settings, vBSecurity can easily be called one of the most comprehensive security suites for your vBulletin forum.

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

If you like this mod please hit the button to the right ---->

Please remember to click the, button to the right if you installed the mod ---->

What does 'Marking As Installed' do ?

* It helps you to stay on top of updates - members who have installed modifications will be notified by us whenever new updates are available.

* For security issues - vbulletin.org will contact all members who have installed a modification whenever a security issue is brought to their attention.

* Marking a modification as installed also helps us know how many people are using our work, giving us extra incentive to provide more features and new modifications.

We appreciate the support!
-------------------------------------------------------------------------------------------

Priority support & Product Demos available at: http://www.dragonbyte-tech.com

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

Translations available @ our forum
Support for translations handled by the translator in its respective threads only.

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

Major Features
Administrator Security: .htaccess-like logins for your administrators means that even if they use the same password on multiple sites, malicious users still need a fresh, unique password to log in.

Security Watchers: Keep an eye on the most important aspects of vBulletin: config.php tampering, AdminCP / User Account access attempts, vBulletin Options, User Data, Usergroup Settings and Usergroup Permissions.
Detailed changelogs available for each watcher dealing with changes.
IP Ban, User Ban, Email alerts and temporary forum closure options available for each watcher individually.

Lite
* Searchable list of all AdminCP access attempts
* Searchable list of all failed login attempts
* Searchable list of administrator changes for areas governed by the Security Watchers
* vBOption: IP Address whitelist for AdminCP access
* vBOption: Separate "Closed Reason" for closures that happened due to potential security breaches
* Quick setting page for the most important vBulletin Options security settings
* Quick setting page for the most important Usergroup security settings
* Security Watchers: General - config.php Variable Tampering, AdminCP Access Attempts
* Security Watchers: Logins - Failed Logons, Failed Mass Logons
* Security Watchers: vBOptions - vBulletin Active, Reason For Turning vBulletin Off, Banned Email Addresses, Banned IP Addresses, Use Login "Strikes" System, Whitelisted IP Addresses, Whitelisted IP Addresses - Exclude Super Administrators
* Security Watchers: User Data - User Name, Password, Email, Primary Usergroup, Additional Usergroups, Reputation Level, Warnings, Infractions, Infraction Points, Receive Admin Emails
* Security Watcher Actions: 2 thresholds with individual configuration options, IP Ban / User Ban / Email Webmaster / Close Forum options available for each Watcher option listed above. Some watcher options may not have all actions.

Pro
* Optional .htaccess-like login on a per-administrator basis
* Settings Snapshots - take a "snapshot" of how the vBulletin Options look at the time, instant restore by clicking Load on a previous snapshot
* Security Watchers: Usergroup - Password Expiry, Password History, every usergroup permission group, every "value" permission
* IP Guard: Administrator IP Address authorisation scheme (similar to Steam Guard) - Require email verification for new IP addresses to access the AdminCP, per-administrator disable

-------------------------------------------------------------------------------------------
This mod displays a copyright notification in the footer of all pages which includes:

• 1 Link to DragonByte Technologies homepage
• 1 Link to Product Description page of this modification

[DragonByte Tech]

Are you sure you have no modifications installed that could be causing this?

I'd suggest looking through every plugin from every mod and ensure none of them tamper with that variable, because I've dug through the vB4 code and they do not unset() or set to NULL that variable.

On DBTech we are also using vBSecurity as well as the datastore prefix, and we have no such issues


Fillip

[sivaganeshk]

Vbseo might cause this? Because it also has a cache setting feature and i choosed Memcached in thtat .

[DragonByte Tech]

That is entirely possible, could you try turning off memcached in vBSEO and see if that resolves the issue?

Fillip

[MagicPID]

I can't find the settings for dual-authentication in the mod that is shown here:

https://vborg.vbsupport.ru/attachmen...1&d=1325289905

Where is it?

[DragonByte Tech]

As per the OP, that is a Pro-only feature


Fillip

[sivaganeshk]

Originally Posted by DragonByte Tech

That is entirely possible, could you try turning off memcached in vBSEO and see if that resolves the issue?


Fillip

I tried and disabled Memc'd in vbSEO . but no use.

I still get the config tampering notification.

"$vbulletin->config['Datastore']['prefix'] is new: NULL"

[DragonByte Tech]

In that case I suggest going through all your installed mods and see if any of them make any such modifications to the $vbulletin->config array


Fillip

[sivaganeshk]

Originally Posted by DragonByte Tech

In that case I suggest going through all your installed mods and see if any of them make any such modifications to the $vbulletin->config array


Fillip

That's difficult buddy
how to check each and individual plugin ???

[DragonByte Tech]

It's what has to be done, unfortunately.

The error is not with vBSecurity, it's working as intended

You can turn off the notification for config.php variable tampering of course, but that would reduce the security of your forum, especially considering you already have one security breach going on (the tampering you keep getting notifs for).


Fillip

[sivaganeshk]

Originally Posted by DragonByte Tech

It's what has to be done, unfortunately.

The error is not with vBSecurity, it's working as intended

You can turn off the notification for config.php variable tampering of course, but that would reduce the security of your forum, especially considering you already have one security breach going on (the tampering you keep getting notifs for).


Fillip

Hmm.. I understand. I had been using vbSecurity for 4 months.
Haven't got this issue until I started using Memcached and changed the datastore settings in config.php

May be, vbSecurity stored old config content , checks new config content and raises the notification.