Skip to content

Technology

Payment Application Data Security Standard

Last fetched

Payment Application Data Security Standard is a technology in WhisperGraph's PredictLeads-derived TECHNOLOGY corpus, categorized under data security, with a published adopter count of 315 hostnames.

Profile

Broader grouping
accounting and finance, security
Published adopter count
315

Payment Application Data Security Standard (PA-DSS) was a security standard created by the PCI Security Standards Council to help software vendors build payment applications that protect cardholder data. It provided rules to prevent storing sensitive information and supported compliance with broader PCI DSS requirements. PA-DSS was mainly used for securing retail and online payment apps. It was officially retired in October 2022.

Vendor site: https://listings.pcisecuritystandards.org/minisite/en/docs/PA-DSS_v3.pdf

Sample adopters

20 hostnames WhisperGraph observed running Payment Application Data Security Standard, a sample of the 315 published adopters.

Hosting concentration

The networks announcing the IP addresses of a sample of 20 Payment Application Data Security Standard adopters, not of all 315 published adopters. A hostname counts once per network.

Related pages

Pivot from Payment Application Data Security Standard into its category and the vendor behind it.

Queries

Resolves the slug's technology-name candidate(s) and projects the winner's fields.


MATCH (t:TECHNOLOGY)
WHERE t.name =~ $pattern
WITH t ORDER BY t.adopterCount DESC, t.name ASC
WITH collect(t)[0] AS winner, count(t) AS candidates
RETURN winner.name AS name,
       winner.description AS description,
       winner.category AS category,
       winner.parentCategories AS parentCategories,
       winner.adopterCount AS adopterCount,
       winner.url AS url,
       winner.vendorApex AS vendorApex,
       candidates
Run yourself →

Reads a 20-host adopter sample and the ASNs announcing its IP addresses.


MATCH (:TECHNOLOGY {name: $name})<-[:RUNS_TECHNOLOGY]-(h:HOSTNAME)
WITH h LIMIT 20
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
RETURN h.name AS host, a.name AS asn
LIMIT 200
Run yourself →

Or query Whisper from your own LLM workflow via the Whisper MCP server.