Sha256: 2cec98b3552ee51495043fa5efcfb8275ffbf99d34d2ea224b2dbba64697d599
Contents?: true
Size: 1.57 KB
Versions: 6
Compression:
Stored size: 1.57 KB
Contents
# frozen_string_literal: true
##
# This file is part of WhatWeb and may be subject to
# redistribution and commercial restrictions. Please see the WhatWeb
# web site for more information on licensing and terms of use.
# http://www.morningstarsecurity.com/research/whatweb
##
WhatWeb::Plugin.define "USP-Secure-Entry-Server" do
@author = "Brendan Coles <bcoles@gmail.com>" # 2011-08-25
@version = "0.1"
@description = "United Security Providers (USP; previously known as Tetrade) Secure Entry Server (SES) Web Application Firewall (WAF)"
@website = "http://www.united-security-providers.com/"
# The United Security Providers (USP; previously known as Tetrade) components Secure Entry Server (SES) and Secure Login Service (SLS) share their tasks in order to adhere to the principles of separation of powers. The task of the SES is to recognize non-authenticated users and to ensure that they are authenticated by the SLS (Access Control Enforcement Function). The task of the SLS is to perform the authentication (Authentication and Access Control Decision Function). The communication between SES and SLS is based on custom HTTP headers. The SES sends the desired user login type to the SLS which performs the authentication. Once the login is completed, the SLS signals the success or failure of the process back to the SES. According to this, the SES determines the access rights of the user.
# ShodanHQ results as at 2011-08-25 #
# 56 for Secure Entry Server
# Matches #
@matches = [
# HTTP Server Header
{ search: "headers[server]", regexp: /^Secure Entry Server$/ },
]
end
Version data entries
6 entries across 6 versions & 1 rubygems