17.20 - Gateway Processing of Restrictive Filters - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database Security Administration - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-03-07
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
  1. The Teradata Vantage gateway tests the incoming IP address against each allow element.
    1. The filter masks the incoming IP address with the mask from the allow element.
    2. The filter masks the IP address in the allow element with the same mask.
    3. If the result for the two masked IP addresses match, the filter identifies the IP address under test as a candidate for approval. The filter then ends the allow phase of testing and begins deny testing of the incoming IP address.
  2. The gateway tests the incoming IP address against each deny element.
    1. The filter masks the incoming IP address under test with the mask from the deny element.
    2. The filter masks the IP address from the deny element with the same mask.
    3. If the result for two masked IP addresses match, the filter allows the IP address under test to access the database and ends the denial phase of testing.
Although you can construct a restrictive filter using both allow and deny elements, you do not have to use both elements in a restrictive filter. A restrictive filter must contain at minimum either an allow or a deny element. If you use only a single element, it should be the primary element type for the filter type, that is, an allow element in a restrictive filter.