RidgeStar
About
Locations
Manual
Preface
Introduction
Versions
Concepts
Construction
Usage
Operations
Questions
Features
Settings
Album
Alerts
Assignments
AssignmentMeter
Assignor
Audit
Auditing
Availability
BulkLoad
BulkMail
Calendar
Chapter
Chart
Criteria
Data
Daylight
Directory
Evaluation
Exams
GeoCode
GoogleAPI
HackDetection
iCalendar
IPMapping
JavaNames
KeyTranslation
Lists
Locations
Mail
MinorAuth...
Misconducts
MissingReports
NACHA
News
NewUsers
Notification
Notify
NWS
PageHeader
Paperwork
Password
PhotoUse
Profile
Questions
Request
Reset
RestClients
RestServer
RMA.WSYSA
Rules
Save
ScheduleMeter
SiteOperations
SoapClients
SoapServer
SRC
Tickets
Timeout
Topics_Upgrade
TouchLine
Translate
Turnback
UserName
USSF_API
Internals
Appendices
Reference
Service
Logon
RidgeStar

Manual: Settings-HackDetection

Logontranslate
Get Started |Calendar |Locations

The HackDetectionFeature Settings controls the function and operation of the HackDetection mechanism, as follows:

Delay
When a single IP Address has exceeded the allowable Hits during the specified Interval, the page response (answer) will be delayed by a Delay number of seconds, The actual delay is computed as Delay*(page-accesses/Hits), which will cause the actual response delay to gradually increase (to act as a deterrent).

Default is 5

Hacking
Establishes the number of distrnct page Hits within the Interval that are permitted before the accessing IP Address is reported as a source of Hacking efforts. If the number of Hacking efforts increases beyond acceptable limits, the IP Address is subject to IP Blockage at the RidgeStar firewall, which will prohibit any access to any RidgeStar Service.

Default is 50

Hits
The number of Hits that defines the maximum allowable page accesses for each individual page during the specified Interval.

Default is 10

Interval
Establishes the period of time relative to the then current time that Hits will be counted.

Default is -5 minutes

PageNames

Default is empty (none specified)