個人データの発見
読了まで約89 分分、13 節 節の 11 例 例。
このページの内容
- スキーマから列を分類する
- Run Presidio offline
- 列の値を毎回同じ方法でサンプリングする
- 値から列を分類する
- Measure a detector against labelled spans
- 認識器を正解データに照らして調整する
- See where patterns fail
- Compare a PII model
- Read the model's misses
- Count what a wrong label costs
- Classify again when the schema changes
- What goes wrong in production
- What this chapter decided
この章を読み終えると、データ基盤上の個人データを自動的に見つけ、その検出でどれだけ見落とすかを示せるようになる。列の名前、型、再現可能な値のサンプルから、すべての列の分類案を作る。自由記述テキストの中の個人データを、スパンごとに見つける。そして、誰かが検出器を信頼する前に、ラベル付きデータで各検出器を測定する。その過程で、測定によって選んだしきい値を使い、Presidio のパターン認識器をオフラインで実行する。その結果を、個人データを見つけるよう訓練されたモデルの記録済みの検出結果と比較する。さらに、スキーマ変更で追加された列だけを再度分類する。
プラットフォーム上のすべての列には、すでに分類がある。第2章で、人がレビューするファイルである governance/metadata.toml に分類を記録した。レビュー済みのファイルが記録するのは、列に何が入っているかについてレビュー担当者が信じている内容である。本書がウェアハウスを統制する対象であるオンライン学習プラットフォームでは、それらの認識のうち3つは、これまで一度も確認されていない。billing.payments.card_number はレガシーの列で、説明にはカード番号の全桁が入っていると書かれているが、誰も中身を確認していない。crm.learners.notes はサポート担当者が入力する自由記述テキストであり、列名からは中身が何も分からない。学習者はサポートチケットやコースレビューに好きなことを書く。列全体に対する分類では、そのテキストを守れない。マスキングする前に、プラットフォームは名前、メールアドレス、電話番号をスパンごとに見つけなければならない。第9章では、コースのアシスタントがレビューから学習する前に、レビューに対してこの処理を行う。
この章では、この作業のために本書で共有するモジュール lib.pii を作る。モジュールには、列名に対するルール、列の値をシード付きで抽出するサンプリング、オフラインで動くよう設定した Presidio の検出器、そして任意の検出器をラベル付きデータに対して採点するコードが含まれる。この章のすべての検出器は、正解データと呼ぶ1つのファイル data/platform/pii_spans.parquet に対して測定する。プラットフォームのデータ生成器は、チケットやレビューと並べてこのファイルを書き出す。ファイルには、生成器がテキストに埋め込んだすべての個人データが、正確な開始位置と終了位置とともに記録されている。請求書番号、注文番号、問題が起きた日付にはラベルを付けない。プラットフォームがこれらを個人データとして扱わないためである。
データカードに記されているとおり、本書の電話番号、カード番号、IBAN はランダムに生成した値である。どの例も、これらを全桁は表示せず、末尾4桁以外を伏せ字にして表示する。
スキーマから列を分類する
列に関する最も安価な根拠は、その列のスキーマ、すなわち名前と型である。名前に対する規則はデータを読まないため、プルリクエストの中でカタログ全体に対して実行できる。また、email や date_of_birth のように、名前が保持する内容を表している列を捕捉できる。カタログツールも同じところから始める。OpenMetadata の自動分類は、列名を正規表現と照合する列名スキャナから始まる(OpenMetadata docs)。次に何をするかは型によって決まる。テキスト列の値はサンプリングしてスキャンできるが、タイムスタンプにメールアドレスが入ることはなく、日付のパターンでスキャンすると全行にフラグが立ってしまう。そのため、数値、日付、タイムスタンプ、真偽値は名前だけで分類する。
プラットフォームは規則を governance/pii.toml に保持する。このファイルは検出器のすべての設定を含み、メタデータと同様にレビューされる。規則は、小文字化した列名に対する 8 個の正規表現であり、それぞれが示唆するエンティティを指定し、最初に一致したものが採用される。同じファイルが各エンティティを分類に対応付ける。電話番号は personal に、カード番号や IBAN は sensitive に対応付けられる。lib.pii.by_name がこれらの規則を適用する。規則はカタログのすべての列に適用され、その結果はレビュー済みのメタデータの隣に置かれる。
1"""Runs the name rules over every column of the catalog and compares each column they mark with the reviewed metadata.2The prose rests on the count of marked columns that agree, and on the personal columns no rule marks."""3from pyiceberg.types import StringType45from lib import metadata, pii6from lib.catalog import open_catalog78catalog = open_catalog()9described = metadata.load() # the reviewed metadata, keyed by table and then by field ID10# every column as (table, field): the field carries the ID the metadata is keyed by, so a renamed column still matches11columns = [(table, f) for (namespace,) in sorted(catalog.list_namespaces())12 for _, name in sorted(catalog.list_tables(namespace))13 for table in [f"{namespace}.{name}"] for f in catalog.load_table(table).schema().fields]14print("columns in the catalog:", len(columns))15print("name rules:", len(pii.NAME_RULES))1617named = [(table, f, pii.by_name(f.name)) for table, f in columns if pii.by_name(f.name)]18print("columns a name rule marks:", len(named))19for table, f, entity in named:20 print(f" {table}.{f.name}: {entity}, so {pii.CLASSIFICATION[entity]}")21agree = sum(pii.CLASSIFICATION[entity] == described[table].columns[f.field_id].classification22 for table, f, entity in named)23print("of them, agreeing with the metadata:", agree)2425# Only text is sampled: numbers, dates, timestamps and booleans are classified by name alone.26text = [(table, f) for table, f in columns if isinstance(f.field_type, StringType)]27print("columns of text, whose values can be sampled:", len(text))2829# Columns the metadata, reviewed by people, calls personal or sensitive, that no name rule marks.30missed = [f"{table}.{f.name}" for table, f in columns if not pii.by_name(f.name)31 and described[table].columns[f.field_id].classification in ("personal", "sensitive")]32print("personal columns no name rule marks:", ", ".join(missed))
python column-name-rules.pycolumns in the catalog: 64
name rules: 8
columns a name rule marks: 11
billing.payments.card_number: CREDIT_CARD, so sensitive
crm.instructors.full_name: PERSON, so personal
crm.instructors.email: EMAIL_ADDRESS, so personal
crm.instructors.payout_iban: IBAN_CODE, so sensitive
crm.learners.full_name: PERSON, so personal
crm.learners.email: EMAIL_ADDRESS, so personal
crm.learners.phone: PHONE_NUMBER, so personal
crm.learners.city: LOCATION, so personal
crm.learners.street_address: LOCATION, so personal
crm.learners.date_of_birth: DATE_TIME, so personal
learning.events.ip_address: IP_ADDRESS, so personal
of them, agreeing with the metadata: 11
columns of text, whose values can be sampled: 29
personal columns no name rule marks: crm.learners.notes, learning.reviews.body, support.tickets.body
規則は、作動した箇所ではメタデータと一致するが、自由記述テキストは見逃す。カタログの 64 個の列のうち、規則が印を付けるのは 11 個であり、そのうち 11 個すべてが、人が付けた分類と一致している。一方、レビュー担当者が personal と分類した3つの列、すなわち crm.learners.notes、learning.reviews.body、support.tickets.body は見逃される。3つとも自由記述テキストであり、名前は中身ではなく入れ物を表している。印が付いた列のうちプラットフォームが最も懸念する billing.payments.card_number は、何が入っているかを誰も確かめないまま、名前だけで sensitive とされる。カード番号の全桁、下4桁、決済プロバイダのトークンのいずれも card_?(number|num|no) に一致してしまう。
名前の規則には、既知の脆さがある。列の型を検出するモデル Sherlock の著者らは、名前の照合はダーティなデータに対して頑健ではなく、検出できる型もわずかであると報告している(Hulsebos et al., 2019)。そのためプラットフォームは、カタログが保持する 29 個のテキスト列については値も読む。
実践ルール: 名前の規則はコストがかからないので、まずすべての列に適用する。ただし、規則は分類を引き上げるだけにし、引き下げてはならない。規則は短く保ち、コードとして管理し、ほかの規則と同様にレビューする。自由記述の列は、その名前にかかわらず、値のサンプリングが必要なものとして扱う。ほかの型の列は名前だけで分類する。
この部分はまだ翻訳されていないため、英語で表示している。
Run Presidio offline
To read values, the platform uses Presidio, an open-source library for finding and masking personal data. Presidio's analyzer runs recognizers: regular expressions with checksums, phone-number parsing, and a named-entity model reached through an NLP engine. The NLP engine does two jobs, named-entity recognition and feature extraction for rules, such as the context words that raise a score. Its default model is spaCy's en_core_web_lg (Presidio docs). At 2.2.366, AnalyzerEngine() with no arguments downloads that model when it isn't installed (source). So a pipeline without network access fails on its first line, and one with access installs a model of about 400 MB as a side effect (en_core_web_lg 3.8.0).
lib.pii.detector configures the engine itself, with NoOpNlpEngine, which loads no language model (source). What that costs is context. With a model, Presidio raises a pattern's score when a word such as "phone" appears near the match, by comparing the lemma of each nearby word with each recognizer's context terms (Presidio's tutorial on context). With no model there are no lemmas, so the engine can't use the text's context words at all. The engine has one more way onto the network. Its email recognizer checks domains with tldextract, which fetches the Public Suffix List the first time it's used (tldextract 5.4.0's README). Importing Presidio imports tldextract, whose README says an empty TLDEXTRACT_PUBLIC_SUFFIX_LIST_URLS turns the fetch off if it's set before the import. So lib/__init__.py, which Python runs before any module of the book's lib, empties the variable. If an example imported Presidio first, the same file replaces tldextract's shared extractor with one that has no URLs. lib.pii refuses to load if any remain, and tldextract uses the copy of the list it ships with, so the same text gives the same answer on every machine.
The defaults are tested on real text: load every predefined recognizer on one of the platform's support tickets, which holds a name, an email, a phone number and a date:
1"""Loads Presidio's predefined recognizers on an engine that loads no language model, and runs them on one support2ticket. The prose's point rests on the detections printed under the ticket, and on the assert that the model isn't3installed."""4import spacy56from lib import pii7from lib.platform import load89# AnalyzerEngine() with no arguments loads spaCy's en_core_web_lg, and downloads it when it isn't installed.10installed = spacy.util.is_package("en_core_web_lg")11assert installed is False # the pipeline assumes no model: a machine that has one fails here, not silently12print("en_core_web_lg installed:", installed)13print("URLs tldextract would fetch the Public Suffix List from:", len(pii.suffix_list_urls()))1415detector = pii.detector() # every predefined recognizer, on an NLP engine that loads no model16names = sorted(r.name for r in detector.registry.recognizers)17print("recognizers loaded:", len(names))18print("recognizers:", ", ".join(names))19print("default score threshold:", detector.default_score_threshold)2021# The ticket holds a phone number, which may be in service: masked() prints it with only its last four digits.22ticket = pii.texts("tickets")[1421] # one ticket with a name, an email, a phone number and a date of the problem23found = sorted(pii.detect(detector, ticket))24print("ticket 1421:", pii.masked(ticket))25for start, end, entity, score in found:26 print(f" {entity} on {pii.masked(ticket[start:end])}: {score:.2f}")2728# Where is the phone number valid? The recognizer reads it in each of its regions.29phone = next(ticket[start:end] for start, end, entity, _ in found if entity == "PHONE_NUMBER")30[learner] = [row["learner_id"] for row in load("support.tickets").to_pylist() if row["ticket_id"] == 1421]31[country] = [row["country"] for row in load("crm.learners").to_pylist() if row["learner_id"] == learner]32print("the learner's country:", country)33# The recognizer's built-in regions, not the learner's country.34print("default regions where it's valid:",35 ", ".join(r for r in pii.PhoneRecognizer.DEFAULT_SUPPORTED_REGIONS if pii.valid_phone(phone, r)))
python presidio-offline-engine.pyen_core_web_lg installed: False
URLs tldextract would fetch the Public Suffix List from: 0
recognizers loaded: 17
recognizers: CreditCardRecognizer, CryptoRecognizer, DateRecognizer, EmailRecognizer, IbanRecognizer, IpRecognizer, MacAddressRecognizer, MedicalLicenseRecognizer, NhsRecognizer, PhoneRecognizer, UrlRecognizer, UsBankRecognizer, UsItinRecognizer, UsLicenseRecognizer, UsPassportRecognizer, UsSsnRecognizer, UuidRecognizer
default score threshold: 0
ticket 1421: I can't open the videos in Introduction to Design Systems, they stop after a few seconds. It happened on 12/03 around 9pm. My colleague Jennifer Abbott (jennifer.abbott@example.net) wants to enrol as well. You can reach me on •••••••0440 after 6pm.
DATE_TIME on 12/03: 0.10
EMAIL_ADDRESS on jennifer.abbott@example.net: 1.00
URL on example.net: 0.50
PHONE_NUMBER on •••••••0440: 0.40
US_BANK_NUMBER on •••••••0440: 0.05
US_DRIVER_LICENSE on •••••••0440: 0.01
the learner's country: US
default regions where it's valid: BR
Presidio's defaults on this engine see the email and the phone number, and miss the colleague's name. en_core_web_lg isn't installed, so a bare AnalyzerEngine() would try to download it, and tldextract has 0 URLs to fetch its list from. The no-model engine loads 17 recognizers, and none of them looks for names, so Jennifer Abbott, the colleague in the ticket, goes unnoticed. Her email is found with a score of 1.00, and its domain is found again as a URL, at 0.50. The learner's phone number, an 11-digit number typed without separators, is found three times: as a phone number at 0.40, a US bank number at 0.05 and a US driver's licence at 0.01. Even the phone number is found by chance. The learner's country is US, but of Presidio's default regions, the US among them, the digits are valid only in BR. The date of the problem, 12/03, is read as a date too, which says nothing about anyone.
Those scores aren't probabilities. Each pattern carries a constant score, and weak patterns get low ones, as Presidio's tutorial explains for a five-digit zip code (Presidio docs). A US bank number is any run of 8 to 17 digits (supported entities), and the FAQ admits that a driver's licence "could be any 9-digit number" (FAQ). The analyzer's default threshold is 0, so every weak match comes back.
Working rule: Configure Presidio's engine explicitly: NoOpNlpEngine when you run patterns only, or a pinned model you install yourself when you need its names. Never call AnalyzerEngine() bare in a pipeline, and pin anything a recognizer would download, such as the Public Suffix List. Read each score as a constant set for its pattern, never as a probability.
列の値を毎回同じ方法でサンプリングする
すべてのテキスト列のすべての値を走査することは、どのウェアハウスにとっても遅すぎる。そのため、各ツールはサンプリングを行う。OpenMetadata のワークフローは行をサンプリングし、エンティティ認識エンジンで検査する(OpenMetadata docs)。サンプルには三つの決定が必要である。どの行か: 無作為なサンプルであり、先頭の行や、ランダムな位置から始まる連続ブロックではない。Google の Sensitive Data Protection には、ランダムな行から読み始めて先へ進むランダムスタートのモード RANDOM_START がある(Google Cloud docs)。登録日順に並んだテーブルでは、そのブロックは学習者の一つのコホートになってしまう。毎回同じ行か: 分類を再現でき、分類が変わったときはデータが変わったことを意味するようにするためである。そして何行か: 検出すべきデータがどれだけ稀かによって決まる。
DuckDB のリザーバサンプルはシードを受け取る。ただし、DuckDB 2.0.0 docs が警告しているとおり、シードによってサンプルが再現できるのは、DuckDB が単一スレッドで動作する場合に限られる。lib.pii.sample は、スレッド数を 1 に設定し、NULL を除外したうえで、シード付きのリザーバサンプルを抽出する。
稀な値にはより大きなサンプルが必要であり、どれだけ大きくすべきかは計算で求められる。個人データを含む値の割合を p とする。サンプルした n 個の値にそれが少なくとも一つ含まれる確率は次のとおりである。
chance = 1 − (1 − p)ⁿ
また、99% の確率を与える n は ln(0.01) / ln(1 − p) である。これは経験則である。各抽出が独立であると仮定しているが、数千行からの非復元抽出であれば、ほぼその仮定が成り立つ。
この式を実際に使ってみる。crm.learners からメモを 20 件、2 回抽出し、全行に対する確率とメモだけに対する確率を比較する。
1"""Draws the same twenty notes twice from a seeded reservoir sample, then counts the notes that hold personal data, to see2how many sampled values a rare value needs. The prose rests on the assert that the draws match, the two chances and the sample sizes."""3import math45from lib import pii6from lib.catalog import open_catalog7from lib.warehouse import connect89con = connect(open_catalog(["crm.learners"]))10first = pii.sample(con, "crm.learners", "notes", rows=20)11second = pii.sample(con, "crm.learners", "notes", rows=20) # the same call: the seed and one thread (set in lib.pii.sample) make the draws match12assert second == first13print("second draw, same notes as the first:", "yes" if second == first else "no")14# Notes can hold a phone number, which may be in service: masked() prints it with only its last four digits.15print("first sampled notes:", " | ".join(pii.masked(note) for note in first[:3]))1617# How rare is personal data in the column? Run the detector over every note, once, to know.18detector = pii.platform_detector()19[(rows, notes)] = con.sql("select count(*), count(notes) from crm.learners").fetchall() # count(notes) skips NULLs20every_note = [note for (note,) in con.sql("select notes from crm.learners where notes is not null").fetchall()]21holding = sum(bool(pii.detect(detector, note)) for note in every_note)22print("learners:", f"{rows:,}")23print("learners with notes:", notes)24print("notes holding personal data the detector finds:", holding)2526# The chance that n sampled values hold at least one of them is 1 - (1 - p)^n, for a share p of the values.27for unit, p in (("rows", holding / rows), ("notes", holding / notes)): # p counted over all learners, then over the notes28 print(f"chance 20 sampled {unit} catch one:", f"{1 - (1 - p) ** 20:.1%}")29 print(f"sampled {unit} needed for a 99% chance:", math.ceil(math.log(0.01) / math.log(1 - p))) # solves for n30print("values the platform samples per text column:", pii.ROWS)31# The rarest share p that a sample of ROWS values still catches 99% of the time, printed as 1 in a whole number.32print("rarest share that sample catches 99% of the time:", f"1 in {math.floor(1 / (1 - 0.01 ** (1 / pii.ROWS)))}")
python seeded-column-sample.pysecond draw, same notes as the first: yes
first sampled notes: VIP: bought a team licence. | Asked about invoices for their employer. | Called about a refund, call back on (•••)•••-1366x•••.
learners: 5,000
learners with notes: 527
notes holding personal data the detector finds: 138
chance 20 sampled rows catch one: 42.9%
sampled rows needed for a 99% chance: 165
chance 20 sampled notes catch one: 99.8%
sampled notes needed for a 99% chance: 16
values the platform samples per text column: 200
rarest share that sample catches 99% of the time: 1 in 43
抽出は繰り返されるので、サンプルを監査できる。同じシードを使えば、2 回目の抽出でも同じ 20 件のメモが返り、3 件目のメモにはすでに電話番号が含まれている。出力ではそれをマスクしている。
5,000 人の学習者のうち、527 人にメモがあり、そのうち 138 件に、本章の後半で調整するプラットフォームの検出器が見つける個人データが含まれている。NULL はサンプルを薄める。NULL には個人データが含まれ得ないためである。20 行をサンプリングすると、42.9% の確率で個人データを捕捉でき、99% の確率にするには 165 行が必要である。実在するメモだけで数えると、20 件で 99.8% の確率で捕捉でき、99% には 16 件で足りる。
実践ルール: NULL でない値を、固定したシードで、単一スレッドでサンプリングし、シードを結果とともに保存する。サンプルのサイズは、検出すべき最も稀な個人データから、99% の場合は n = ln(0.01) / ln(1 − p) で決める。このプラットフォームはテキスト列ごとに 200 個の値をサンプリングする。この値は governance/pii.toml で設定されており、1 in 43 個以上の値が保持する個人データを 99% の確率で捕捉する。それより稀なものについては、列全体を走査するか、ルールで分類する。
値から列を分類する
名前の規則と再現可能なサンプルを組み合わせると、列ごとに一つの提案が得られる。lib.pii.classifyは、どちらかが裏づける分類のうち最も厳しいものを採用する。すなわち、名前が示すエンティティと、サンプリングした値のいずれかから見つかったすべてのエンティティである。証拠のない列にはinternalを付ける。何も見つけられなかった検出器は何も示していないからであり、列がpublicであると判断するのは人だけだからである。
最も厳しいものを採ることは一つの選択である。Presidio 自身のテーブル向けツールである Presidio structured は、列ごとに一つのエンティティを割り当てる。その既定値である Most Common は、最も頻繁に現れるエンティティを選ぶ(Presidio docs)。これは列をどうマスクするかを選ぶ場合には適している。しかし分類の場合、200 個の値のうち 1 個でもカード番号を含む列は、やはりカード番号を含む列である。
プラットフォームの検出器を用いてカタログのすべての列について提案を出し、レビュー済みのメタデータとどこが異なるかを示す。検出器が使う認識器は後の節で選ぶ。
1"""Proposes a classification for every column, the strictest of what its name and its sampled values support, and compares2each proposal with the reviewed metadata. The prose's table rests on the proposed and found lines of each column, and3its counts on the totals printed after them."""4from lib import metadata, pii5from lib.catalog import open_catalog6from lib.warehouse import connect78catalog = open_catalog()9findings = pii.classify(catalog, connect(catalog), pii.platform_detector()) # the platform's tuned detector, not the defaults10print("columns classified:", len(findings))11print("columns sampled:", sum(f.sampled > 0 for f in findings))1213holding = [f for f in findings if f.found] # columns where sampled values hold personal data14print("columns whose sampled values hold personal data:", len(holding))15# A column counts when its values hold an entity other than the one its name suggests (named is None when no rule matches).16print("of them, holding something their name doesn't suggest:", sum(set(f.found) != {f.named} for f in holding))17for f in holding:18 print(f"{f.table}.{f.column}, proposed: {f.classification}")19 print(f"{f.table}.{f.column}, found: " + ", ".join(f"{e} in {n} of {f.sampled}" for e, n in f.found.most_common()))20[cards] = [f for f in findings if f.column == "card_number"] # the one card_number column in the catalog21# The card recognizer's count: values that match its pattern and pass its Luhn check, out of the values sampled.22print("sampled card numbers the card recognizer accepts:", f"{cards.found['CREDIT_CARD']} of {cards.sampled}")2324# Classifications the values raise above what the name alone gives: the floor is used for a name no rule matches.25named_only = [f for f in findings if pii.CLASSIFICATION.get(f.named, pii.FLOOR) != f.classification]26print("columns the values classify more strictly than the name:", ", ".join(f"{f.table}.{f.column}" for f in named_only))2728# Compare with the metadata people reviewed. A column the detector found nothing in proposes only the floor, internal.29described = metadata.load()30evidenced = [f for f in findings if f.named or f.found]31print("columns with evidence:", len(evidenced))32print("of them, equal to the metadata:",33 sum(f.classification == described[f.table].columns[f.field_id].classification for f in evidenced))34for f in evidenced:35 reviewed = described[f.table].columns[f.field_id].classification36 if metadata.stricter(f.classification, reviewed) != reviewed: # the stricter of the two: a lower proposal prints nothing37 print(f"stricter than the metadata, {f.table}.{f.column}: {f.classification}, reviewed as {reviewed}")
python classify-sampled-columns.pycolumns classified: 64
columns sampled: 29
columns whose sampled values hold personal data: 9
of them, holding something their name doesn't suggest: 5
billing.payments.card_number, proposed: sensitive
billing.payments.card_number, found: CREDIT_CARD in 151 of 200, PHONE_NUMBER in 3 of 200
crm.instructors.email, proposed: personal
crm.instructors.email, found: EMAIL_ADDRESS in 50 of 50
crm.instructors.payout_iban, proposed: sensitive
crm.instructors.payout_iban, found: IBAN_CODE in 50 of 50
crm.learners.email, proposed: personal
crm.learners.email, found: EMAIL_ADDRESS in 200 of 200
crm.learners.phone, proposed: personal
crm.learners.phone, found: PHONE_NUMBER in 175 of 200
crm.learners.notes, proposed: personal
crm.learners.notes, found: PHONE_NUMBER in 29 of 200, EMAIL_ADDRESS in 18 of 200
learning.events.ip_address, proposed: personal
learning.events.ip_address, found: IP_ADDRESS in 200 of 200, PHONE_NUMBER in 39 of 200
learning.reviews.body, proposed: personal
learning.reviews.body, found: EMAIL_ADDRESS in 4 of 200
support.tickets.body, proposed: sensitive
support.tickets.body, found: EMAIL_ADDRESS in 47 of 200, PHONE_NUMBER in 37 of 200, DATE_TIME in 29 of 200, IBAN_CODE in 21 of 200, CREDIT_CARD in 12 of 200
sampled card numbers the card recognizer accepts: 151 of 200
columns the values classify more strictly than the name: crm.learners.notes, learning.reviews.body, support.tickets.body
columns with evidence: 14
of them, equal to the metadata: 13
stricter than the metadata, support.tickets.body: sensitive, reviewed as personal
名前だけでは決まらない部分は、値によって決まる。サンプルに個人データが含まれる9列のうち、いくつかはcrm.learners.emailのように、名前のとおりのものしか含まない。残りの5列は、名前からは想定できないものを含むか、名前が何も示唆しない。
| 列 | 提案 | サンプルで見つかったもの |
|---|---|---|
billing.payments.card_number |
sensitive | CREDIT_CARD in 151 of 200, PHONE_NUMBER in 3 of 200 |
crm.learners.notes |
personal | PHONE_NUMBER in 29 of 200, EMAIL_ADDRESS in 18 of 200 |
support.tickets.body |
sensitive | EMAIL_ADDRESS in 47 of 200, PHONE_NUMBER in 37 of 200, DATE_TIME in 29 of 200, IBAN_CODE in 21 of 200, CREDIT_CARD in 12 of 200 |
learning.reviews.body |
personal | EMAIL_ADDRESS in 4 of 200 |
learning.events.ip_address |
personal | IP_ADDRESS in 200 of 200, PHONE_NUMBER in 39 of 200 |
旧カード列の説明には「そもそも保存すべきではない」とあり、サンプルからは完全なカード番号が含まれていることが分かる。これに対しては、テーブルの所有者であるteam-billingが対処できる。サンプリングしたカード番号のうち151 of 200は Presidio のカードパターンに一致し、そのパターンが確認する Luhn チェックサムも通る(source)。残りはパターンが対象としない形式である(パターンが失敗する場所を見る)。notes 列は、値だけからpersonalと判定される。チケット本文はsensitiveである。学習者がカード番号や IBAN をチケットに貼り付けるためであり、これはメタデータより厳しい唯一の提案である。メタデータでは、人がレビューしてpersonalとしていた。何らかの証拠がある14列のうち、レビュー済みの分類と一致するのは13列である。
判定だけでなく証拠も読むこと。一部の IP アドレスは電話番号としても読み取られる。IP アドレスはいずれにせよpersonalであるため、ここでは何も変わらない。しかし、検出器のラベルが示すのは値が何に見えるかであり、値が何であるかではない。
実践ルール: 名前またはサンプリングした値のいずれかが裏づける最も厳しい分類を、internalを下限として提案し、提案とともに証拠を示す。レビュー済みのメタデータより厳しい提案は、テーブルの所有者に対する指摘事項である。所有者は分類を引き上げるか、引き上げない理由を記録する。検出器に分類を下げさせてはならない。OpenMetadata は、すでに PII タグが付いている列をスキップする。これに対して本書では、検証の対象はレビュー済みのタグそのものであるため、毎回の実行ですべてのテキスト列をサンプリングすることを勧める。
この部分はまだ翻訳されていないため、英語で表示している。
Measure a detector against labelled spans
A column-level answer is enough to classify support.tickets.body, but not to mask it: masking replaces each span of personal data in each text, and a span the detector misses stays readable. To know what a detector misses, compare its spans with the truth, the labelled spans of every ticket and review. Two matching rules are standard, and lib.pii applies both.
Exact matching, from the CoNLL-2003 shared task, counts an entity "correct only if it is an exact match of the corresponding entity in the data file" (Tjong Kim Sang and De Meulder, 2003). Overlap matching asks only for one shared character, with a label of its type, which the SemEval-2013 task on drug interactions calls "Type matching" (Segura-Bedmar et al., 2013). Neither credits a span hidden under another label, so lib.pii adds a third measure, coverage: whether every character of a labelled span is inside some detection, whatever its label. Exact asks whether the detector labelled the whole span right, overlap whether it noticed the span as what it is, and coverage whether masking its detections hides the span.
lib.pii.score computes exact and overlap matching as recall, the share of labelled spans of each type that a detector finds with a label of that type, and precision, the share of each label's detections that match a labelled span. lib.pii.coverage gives the share of each type's spans covered. score also counts the texts in which every labelled character falls inside some detection, the texts that masking would leave with nothing personal. The Text Anonymization Benchmark protects a person only when all of their mentions are masked (Pilán et al., 2022), and the platform counts whole texts, which is stricter. Recall comes first: Presidio's evaluation guide says it often matters more than precision, because missing personal data is the error to avoid (Presidio docs).
Presidio's defaults, scored against the labelled spans of every ticket and review, give the baseline the rest of the chapter improves on:
1"""Runs Presidio with its defaults over every ticket and review, and scores its detections against the truth's labelled2spans. The prose rests on the recall and precision lines, the count of texts left with nothing personal, and the two3date lines that test the truth's limits."""4import re56from lib import pii78labelled = pii.truth()9print("texts:", f"{sum(len(pii.texts(source)) for source in pii.SOURCES):,}")10print("labelled spans:", f"{len(labelled):,}")1112detector = pii.detector() # Presidio's defaults: every recognizer, threshold 013found = pii.find(detector)14# scoring needs a label of the span's type; coverage doesn't15scores, covered = pii.score(found, labelled), pii.coverage(found, labelled)16print("detections:", f"{len(found):,}")1718for entity, (n, exact, overlap) in scores.recall.items():19 print(f"{entity}, labelled: {n:,}")20 print(f"{entity}, recall, exact: {exact / n:.2f}")21 print(f"{entity}, recall, overlap: {overlap / n:.2f}")22 print(f"{entity}, covered, any label: {covered[entity][1] / n:.2f}") # covered[entity] is (spans, covered), so n is the same count2324for label, (n, exact, overlap) in scores.precision.items(): # precision is per label: what each detection was called25 print(f"{label}, detections: {n:,}")26 print(f"{label}, precision, exact: {exact / n:.2f}")2728# every bank number and driver's licence detection is a false alarm: none matches a labelled span29assert all(scores.precision[entity][1] == 0 for entity in ("US_BANK_NUMBER", "US_DRIVER_LICENSE"))30print("precision of all detections, exact:", f"{pii.precision_overall(scores):.2f}")31print("texts holding personal data:", f"{scores.texts:,}")32print("texts with every labelled span masked:", f"{scores.masked:,}")3334# The truth's limits. The generator builds every text from a few sentence templates, and writes every date of birth35# one way. Presidio's date patterns don't read every way of writing one.36print("sentence templates the texts are built from:", len(pii.templates()))37births = [pii.text_of(s) for s in labelled if s.entity == "DATE_TIME"] # the truth's dates are the dates of birth: dates of a problem are unlabelled38written_ymd = sum(re.fullmatch(r"\d{4}-\d\d-\d\d", d) is not None for d in births) # year first, the generator's one form39assert written_ymd == len(births) # so every date of birth is written this way40print("dates of birth written like 1985-03-12:", written_ymd)41for written in ("1985-03-12", "12 March 1985"):42 text = f"My date of birth on the account is wrong, it should be {written}." # a sentence in the generator's shape43 print(f"dates found in a date of birth written {written}:", sum(e == "DATE_TIME" for _, _, e, _ in pii.detect(detector, text)))
python measure-pattern-recognizers.pytexts: 5,000
labelled spans: 4,292
detections: 3,902
CREDIT_CARD, labelled: 213
CREDIT_CARD, recall, exact: 0.71
CREDIT_CARD, recall, overlap: 0.71
CREDIT_CARD, covered, any label: 0.89
DATE_TIME, labelled: 196
DATE_TIME, recall, exact: 1.00
DATE_TIME, recall, overlap: 1.00
DATE_TIME, covered, any label: 1.00
EMAIL_ADDRESS, labelled: 543
EMAIL_ADDRESS, recall, exact: 1.00
EMAIL_ADDRESS, recall, overlap: 1.00
EMAIL_ADDRESS, covered, any label: 1.00
IBAN_CODE, labelled: 236
IBAN_CODE, recall, exact: 1.00
IBAN_CODE, recall, overlap: 1.00
IBAN_CODE, covered, any label: 1.00
LOCATION, labelled: 210
LOCATION, recall, exact: 0.00
LOCATION, recall, overlap: 0.00
LOCATION, covered, any label: 0.00
PERSON, labelled: 2,455
PERSON, recall, exact: 0.00
PERSON, recall, overlap: 0.00
PERSON, covered, any label: 0.00
PHONE_NUMBER, labelled: 439
PHONE_NUMBER, recall, exact: 0.78
PHONE_NUMBER, recall, overlap: 0.79
PHONE_NUMBER, covered, any label: 0.91
CREDIT_CARD, detections: 151
CREDIT_CARD, precision, exact: 1.00
DATE_TIME, detections: 421
DATE_TIME, precision, exact: 0.47
EMAIL_ADDRESS, detections: 543
EMAIL_ADDRESS, precision, exact: 1.00
IBAN_CODE, detections: 236
IBAN_CODE, precision, exact: 1.00
MEDICAL_LICENSE, detections: 18
MEDICAL_LICENSE, precision, exact: 0.00
PHONE_NUMBER, detections: 384
PHONE_NUMBER, precision, exact: 0.89
UK_NHS, detections: 8
UK_NHS, precision, exact: 0.00
URL, detections: 751
URL, precision, exact: 0.00
US_BANK_NUMBER, detections: 689
US_BANK_NUMBER, precision, exact: 0.00
US_DRIVER_LICENSE, detections: 683
US_DRIVER_LICENSE, precision, exact: 0.00
US_ITIN, detections: 2
US_ITIN, precision, exact: 0.00
US_PASSPORT, detections: 8
US_PASSPORT, precision, exact: 0.00
US_SSN, detections: 8
US_SSN, precision, exact: 0.00
precision of all detections, exact: 0.38
texts holding personal data: 2,586
texts with every labelled span masked: 425
sentence templates the texts are built from: 30
dates of birth written like 1985-03-12: 196
dates found in a date of birth written 1985-03-12: 1
dates found in a date of birth written 12 March 1985: 0
| Entity type | Labelled | Recall, exact | Recall, overlap | Covered |
|---|---|---|---|---|
PERSON |
2,455 | 0.00 | 0.00 | 0.00 |
EMAIL_ADDRESS |
543 | 1.00 | 1.00 | 1.00 |
PHONE_NUMBER |
439 | 0.78 | 0.79 | 0.91 |
IBAN_CODE |
236 | 1.00 | 1.00 | 1.00 |
CREDIT_CARD |
213 | 0.71 | 0.71 | 0.89 |
LOCATION |
210 | 0.00 | 0.00 | 0.00 |
DATE_TIME |
196 | 1.00 | 1.00 | 1.00 |
The defaults find every email, IBAN and date of birth, most phone and card numbers, and no names or street addresses at all, which is most of what the tickets hold. Most of what they flag is wrong: 0.38 of all detections match a labelled span. The 689 US bank numbers, 683 driver's licences and 751 URLs are all wrong. Phone, card and invoice numbers, all runs of digits, come out as bank numbers and licences, and pieces of emails and a few addresses come out as URLs. A wrong label still hides the digits, so phone and card numbers are covered more often than they're found.
Masking would leave personal data in most texts that hold it. Only 425 of the 2,586 texts would come out with nothing personal left.
The truth has its own limits, because the text is generated. Every ticket and review is built from 30 sentence templates in prep/generate.py, so each hard case is one sentence frame, and all 196 dates of birth are written like 1985-03-12. The date recall of 1.00 therefore measures one format: in the generator's own sentence, Presidio finds 1 date when the date of birth is written 1985-03-12, and 0 when it's written 12 March 1985. A measure on this text tells you how a detector behaves on these shapes, not how it will do on yours.
Working rule: Measure every detector against labelled spans before it masks anything: recall per entity type by exact and by overlap matching, both with a label of the right type, coverage whatever the label, precision per label, and the share of texts with nothing personal left. Weigh recall first. Before you trust a detector on your text, label a few hundred real records by hand and measure on those too.
認識器を正解データに照らして調整する
Presidioの既定設定は、弱い一致をすべて返す。FAQは二つの対処法を挙げている。採用しきい値を変更することと、データセットに不要な認識器を取り除くことである。FAQはまた、偽陽性と偽陰性の間にトレードオフがあることにも触れている(FAQ)。Presidio 2.2.364では、認識器ごと、およびエンティティごとのスコアしきい値が追加され、アナライザの既定値がフォールバックとして使われる(変更履歴、リリースノート)。電話番号の認識器には、学習者が多くの国に住むプラットフォームで重要になる設定がもう一つある。読み取る番号体系の地域である(ソース)。
governance/pii.tomlは、プラットフォームのテキストに含まれ得る識別子に対応する6個の認識器を保持し、それぞれに固有のしきい値を設定する。電話番号の地域は設定項目ではない。lib.pii.countriesが、学習者の居住国をcrm.learnersから読み取るので、地域はデータに従う。四つの設定を同じ正解データで採点する。
1"""Scores four detector settings against the same truth: Presidio's defaults, one threshold for every recognizer, the kept2recognizers with their own thresholds, and those with phone numbers read in the learners' countries. The prose rests on3the precision, phone recall, coverage and fully masked texts of each setting."""4from lib import pii56labelled = pii.truth()7print("recognizers kept:", len(pii.THRESHOLDS)) # read from governance/pii.toml8print("recognizers kept, with their thresholds:", ", ".join(f"{name} {t}" for name, t in pii.THRESHOLDS.items()))9print("phone regions, Presidio's default:", ", ".join(pii.PhoneRecognizer.DEFAULT_SUPPORTED_REGIONS)) # Presidio's own list10print("phone regions, the learners' countries:", ", ".join(pii.countries())) # read from crm.learners1112# In the order the prose builds them: the defaults, one threshold, the kept recognizers, then their regions.13settings = {14 "Presidio's defaults": pii.detector(),15 "one threshold of 0.5": pii.detector(default_threshold=0.5),16 "kept recognizers, own thresholds": pii.detector(pii.THRESHOLDS),17 "kept recognizers, learners' phone regions": pii.platform_detector(),18}19for name, detector in settings.items():20 found = pii.find(detector)21 scores, covered = pii.score(found, labelled), pii.coverage(found, labelled)22 n, exact, _ = scores.recall["PHONE_NUMBER"] # the table reads exact recall, so the overlap count is left out23 print(f"{name}, detections: {len(found):,}")24 print(f"{name}, precision, exact: {pii.precision_overall(scores):.2f}")25 print(f"{name}, phone recall, exact: {exact / n:.2f}")26 # coverage takes a detection under any label27 for entity, short in (("PHONE_NUMBER", "phones"), ("CREDIT_CARD", "cards")):28 print(f"{name}, {short} covered, any label: {covered[entity][1] / covered[entity][0]:.2f}")29 print(f"{name}, texts with every labelled span masked: {scores.masked:,}")
python tune-pattern-recognizers.pyrecognizers kept: 6
recognizers kept, with their thresholds: EmailRecognizer 0.5, PhoneRecognizer 0.4, CreditCardRecognizer 0.5, IbanRecognizer 0.5, DateRecognizer 0.5, IpRecognizer 0.5
phone regions, Presidio's default: US, GB, DE, FR, IL, IN, CA, BR
phone regions, the learners' countries: AU, BR, CA, DE, ES, FR, GB, IN, JP, MX, PL, US
Presidio's defaults, detections: 3,902
Presidio's defaults, precision, exact: 0.38
Presidio's defaults, phone recall, exact: 0.78
Presidio's defaults, phones covered, any label: 0.91
Presidio's defaults, cards covered, any label: 0.89
Presidio's defaults, texts with every labelled span masked: 425
one threshold of 0.5, detections: 1,903
one threshold of 0.5, precision, exact: 0.59
one threshold of 0.5, phone recall, exact: 0.00
one threshold of 0.5, phones covered, any label: 0.01
one threshold of 0.5, cards covered, any label: 0.71
one threshold of 0.5, texts with every labelled span masked: 284
kept recognizers, own thresholds, detections: 1,510
kept recognizers, own thresholds, precision, exact: 0.97
kept recognizers, own thresholds, phone recall, exact: 0.78
kept recognizers, own thresholds, phones covered, any label: 0.78
kept recognizers, own thresholds, cards covered, any label: 0.72
kept recognizers, own thresholds, texts with every labelled span masked: 394
kept recognizers, learners' phone regions, detections: 1,539
kept recognizers, learners' phone regions, precision, exact: 0.97
kept recognizers, learners' phone regions, phone recall, exact: 0.84
kept recognizers, learners' phone regions, phones covered, any label: 0.84
kept recognizers, learners' phone regions, cards covered, any label: 0.72
kept recognizers, learners' phone regions, texts with every labelled span masked: 405
| 指標 | 既定設定 | 単一のしきい値 0.5 | 保持した認識器 | さらに学習者の地域 |
|---|---|---|---|---|
| 検出数 | 3,902 | 1,903 | 1,510 | 1,539 |
| 適合率(完全一致) | 0.38 | 0.59 | 0.97 | 0.97 |
| 電話番号の再現率(完全一致) | 0.78 | 0.00 | 0.78 | 0.84 |
| 電話番号の被覆 | 0.91 | 0.01 | 0.78 | 0.84 |
| カード番号の被覆 | 0.89 | 0.71 | 0.72 | 0.72 |
| 完全にマスクされたテキスト | 425 | 284 | 394 | 405 |
明白な修正は失敗する。0.5という単一のしきい値は弱い一致を取り除くが、電話番号もすべて一緒に消える。文脈語がスコアを引き上げない場合、電話番号のスコアは0.40になるからである。6個の認識器だけを残し、それぞれに固有のしきい値を設定して、電話番号のしきい値を電話番号が得るスコアに合わせると、適合率は0.97に上がり、電話番号の再現率は変わらない。Presidioの既定の地域ではなく学習者の地域で電話番号を読み取ると、電話番号の再現率は0.84に上がる。
一つだけ悪化する数値がある。完全にマスクされるテキストが、既定設定よりも減る。除外した認識器は、一部の電話番号やカード番号を誤ったラベルでマスクしていた。それでも数字は隠れる。それらがないと、被覆は電話番号で0.91から0.78に、カード番号で0.89から0.72に下がる。この代償は適合率に見合うと考える。検出結果はレビュー担当者が読む証拠であり、既定設定ではチケットとレビューに689件の銀行口座番号と683件の運転免許番号が含まれるが、実在するものは一つもないからである。governance/pii.tomlはどちらのエンティティも分類に対応づけていないので、提案は変わらないが、それぞれが誰かが読んで却下しなければならない指摘事項になる。米国の認識器を外すことは、プラットフォームのテキストについての主張でもある。正解データには米国の銀行口座番号も免許番号も含まれていない。プラットフォームがいずれかを求めるようになれば、この主張と測定を変えなければならない。
実践ルール: Presidioの既定しきい値0のまま、あるいはすべての認識器に単一のしきい値を使って運用してはならない。テキストに含まれ得る識別子の認識器だけを残し、それぞれのしきい値を各認識器自身のスコアから決め、電話番号はユーザーが住む地域で、データから導出して読み取る。そのすべてをコードに記述し、変更するたびに測定し直す。
この部分はまだ翻訳されていないため、英語で表示している。
See where patterns fail
The tuned recognizers score well on totals, and totals hide where they fail. A pattern detector fails in three ways: there's no pattern for the thing at all, its pattern or its validation rejects the value, or it matches something that only looks personal. The platform's tickets plant cases of each kind, as its data card says: names typed in lowercase, initials, first names that are ordinary words, phone numbers typed without separators, and invoice numbers, order numbers and dates of a problem, which the truth leaves unlabelled. Count each case with the platform's detector. A case counts as caught when some detection overlaps it, whatever its label:
1"""Counts each hard case the tickets and reviews plant, and each look-alike number or date the platform's detector flags,2then checks the card and phone numbers it misses. The prose rests on the caught counts for names and invoice numbers,3and on the misses' lengths, first digits and validity."""4from collections import Counter56from lib import pii7from lib.platform import load89labelled = pii.truth()10found = pii.find(pii.platform_detector())1112cases = pii.hard_cases(labelled) # a case is caught when some detection overlaps it, whatever its label13for case, spans in cases.items():14 print(f"{case}, labelled: {len(spans)}")15 print(f"{case}, caught: {pii.caught(spans, found)}")16print("hard cases of a name, caught:", pii.caught([s for spans in cases.values() for s in spans if s.entity == "PERSON"], found))1718# Look-alikes are numbers and dates that aren't personal data, so any detection on one is a false alarm.19for kind, spans in pii.lookalikes().items():20 print(f"{kind}, in the tickets: {len(spans)}")21 print(f"{kind}, flagged as personal data: {pii.caught(spans, found)}")2223# Card numbers the card pattern misses: too short or long for its 13 to 17 digits, or a first digit it doesn't accept.24# Out of range, the length is the reason; in range, the first digit is, since the pattern accepts only some of them.25missed = pii.missed([s for s in labelled if s.entity == "CREDIT_CARD"], found, {"CREDIT_CARD"})26why = lambda digits: f"{len(digits)} digits" if not 13 <= len(digits) <= 17 else f"{len(digits)} digits starting with {digits[0]}"27print("CREDIT_CARD, missed:", len(missed))28for reason, n in Counter(why(pii.text_of(s)) for s in missed).most_common():29 print(f"CREDIT_CARD, missed, {reason}: {n}")30print("IBAN_CODE, missed:", len(pii.missed([s for s in labelled if s.entity == "IBAN_CODE"], found, {"IBAN_CODE"})))3132# Are the phone numbers the patterns miss valid where the ticket's learner lives? Phones appear only in tickets,33# so each phone's learner comes from its ticket.34learner_of = {row["ticket_id"]: row["learner_id"] for row in load("support.tickets").to_pylist()}35country_of = {row["learner_id"]: row["country"] for row in load("crm.learners").to_pylist()}36phones = pii.missed([s for s in labelled if s.entity == "PHONE_NUMBER"], found, {"PHONE_NUMBER"})37print("phone numbers missed:", len(phones))38print("of them, invalid in the learner's country:",39 sum(not pii.valid_phone(pii.text_of(s), country_of[learner_of[s.row_id]]) for s in phones))
python pattern-hard-cases.pynames in lowercase, labelled: 211
names in lowercase, caught: 0
initial and surname, labelled: 163
initial and surname, caught: 0
first names that are words, labelled: 187
first names that are words, caught: 0
instructors named in reviews, labelled: 798
instructors named in reviews, caught: 0
phones typed as digits only, labelled: 257
phones typed as digits only, caught: 220
hard cases of a name, caught: 0
invoice numbers, in the tickets: 224
invoice numbers, flagged as personal data: 31
order numbers, in the tickets: 212
order numbers, flagged as personal data: 0
dates of a problem, in the tickets: 225
dates of a problem, flagged as personal data: 0
CREDIT_CARD, missed: 62
CREDIT_CARD, missed, 19 digits: 23
CREDIT_CARD, missed, 12 digits: 22
CREDIT_CARD, missed, 16 digits starting with 2: 10
CREDIT_CARD, missed, 15 digits starting with 2: 7
IBAN_CODE, missed: 0
phone numbers missed: 65
of them, invalid in the learner's country: 63
Names are the gap, since no pattern matches a name. Across the names in lowercase, the initials with a surname, the first names that are ordinary words and the instructors named in reviews, the patterns catch 0 of them. Phones typed as digits only do well, 220 of 257. The price is the look-alikes: 31 of the 224 invoice numbers are flagged as personal data.
The platform's detector flags 0 of the 212 order numbers and 0 of the 225 dates of a problem. With Presidio's defaults, 12/03 was a date at 0.10, and the date recognizer returned 421 dates where the truth labels 196. The threshold in governance/pii.toml keeps such weak matches out.
The card pattern's shape causes the card misses. It accepts 13 to 17 digits starting with 1, 3, 4, 50 to 55 or 6, but no 13-digit number starting with 1 (source), and every card number in the data passes the Luhn checksum, so validation rejects none. Of the 62 card numbers it misses, 23 have 19 digits and 22 have 12, and the rest start with 2, which the pattern doesn't accept.
Validation causes the other misses. The IBAN recognizer checks each country's format, length and check digits (source). Every labelled IBAN passes, so it misses 0, but a learner who mistypes one digit writes a value it rejects. The phone recognizer accepts only numbers that python-phonenumbers calls valid (source), and the generator doesn't always write those. Of the 65 phone numbers the detector misses, 63 aren't valid in the country the ticket's learner lives in, so most of the phone misses are the generator's, not the detector's.
Working rule: Read a detector's misses by case, not by total, and keep a list of the cases your text holds. Use patterns for what has a checkable shape, such as emails, IBANs, card numbers, phone numbers and dates, and never for names or addresses. Keep the checksums and numbering plans, because they're what makes the patterns precise. Check the card pattern against the card numbers your payment provider issues, and the date patterns against the ways your users write dates.
この部分はまだ翻訳されていないため、英語で表示している。
Compare a PII model
The patterns have nothing for names or addresses, and those are most of the personal data in the platform's text: 2,455 names and 210 addresses among the 4,292 labelled spans. Finding them takes a model that reads context, not a general named-entity model. The authors of the SPY dataset define PII as the entities that can identify, contact or locate a specific individual, and found that dedicated named-entity models have limits in PII contexts (Savkin et al., 2025). We use a PII model, one trained for personally identifiable information: OpenAI's Privacy Filter, an Apache-2.0 model with eight fixed labels, such as private_person, private_address and account_number (model card).
The labels are the model's own. OpenAI's card says its label policies can't be set while the model runs (OpenAI, 2026, section 4.2). We chose it over GLiNER2-PII, the runner-up among open PII models, for those fixed labels. GLiNER2-PII takes the labels to look for at inference time, along with a threshold (model card), so a recording of it would have to pin both. Privacy Filter has 1.5 billion parameters, 50 million of them active, and runs on a CPU.
The book's examples never run a model, so they read a recording of its output. The recording, data/recorded/pii-entities/, which this chapter and chapter 9 use, holds every span the model found in every ticket and review, with its offsets, its text and the model's label. recordings/pii_entities.py made it on a CPU with the model's reference decoder, opf (code), which chooses the best sequence of labels for a whole text, so most spans come back in one piece rather than token by token. It used the default operating point, with all six transition biases at 0 (calibration file); the model can also be set "for improved recall" (section 2.3.2). The manifest pins the model's revision and the SHA-256 of its weights, so anyone can record it again and compare, and lib.pii.recorded refuses spans that don't match the text at their offsets. The recording keeps the model's labels, and the example maps them to the truth's types, so a different mapping never needs a new recording. Score the model, the platform's patterns and both together, masking whatever either finds:
1"""Scores the recorded spans of OpenAI's Privacy Filter against the truth, alone and beside the platform's patterns. The2prose rests on the recall lines for names, addresses, phones and cards, the precision lines, and the texts left with3nothing personal."""4from lib import pii56# Privacy Filter's eight labels, mapped to the truth's entity types. A label the truth has no type for matches nothing.7MATCHES = {"private_person": {"PERSON"}, "private_email": {"EMAIL_ADDRESS"}, "private_phone": {"PHONE_NUMBER"},8 "private_address": {"LOCATION"}, "account_number": {"CREDIT_CARD", "IBAN_CODE"},9 "private_date": {"DATE_TIME"}, "private_url": set(), "secret": set()}1011model, manifest = pii.recorded("pii-entities") # the model's spans, from a recording: no model runs here12print("model:", manifest["model"], "decoded with", manifest["settings"]["decode_mode"])13labelled = pii.truth()14detectors = {"patterns": pii.find(pii.platform_detector()), "model": model}15# both lists joined: a span either one finds is masked, and a span both find is simply counted twice16detectors["both"] = detectors["patterns"] + model1718for name, found in detectors.items():19 scores = pii.score(found, labelled, MATCHES) # Presidio's labels aren't in MATCHES, so match themselves20 print(f"{name}, detections: {len(found):,}")21 for entity, (n, exact, overlap) in scores.recall.items():22 print(f"{name}, {entity}, recall, exact: {exact / n:.2f}")23 print(f"{name}, {entity}, recall, overlap: {overlap / n:.2f}")24 print(f"{name}, precision, exact: {pii.precision_overall(scores):.2f}")25 print(f"{name}, texts with every labelled span masked: {scores.masked:,} of {scores.texts:,}")2627# Precision by the model's own label: a label that's right for one truth type can still be wrong for another28for label, (n, exact, overlap) in pii.score(model, labelled, MATCHES).precision.items():29 print(f"model, {label}, detections: {n:,}")30 print(f"model, {label}, precision, exact: {exact / n:.2f}")31 print(f"model, {label}, precision, overlap: {overlap / n:.2f}")
python privacy-filter-spans.pymodel: openai/privacy-filter decoded with viterbi
patterns, detections: 1,539
patterns, CREDIT_CARD, recall, exact: 0.71
patterns, CREDIT_CARD, recall, overlap: 0.71
patterns, DATE_TIME, recall, exact: 1.00
patterns, DATE_TIME, recall, overlap: 1.00
patterns, EMAIL_ADDRESS, recall, exact: 1.00
patterns, EMAIL_ADDRESS, recall, overlap: 1.00
patterns, IBAN_CODE, recall, exact: 1.00
patterns, IBAN_CODE, recall, overlap: 1.00
patterns, LOCATION, recall, exact: 0.00
patterns, LOCATION, recall, overlap: 0.00
patterns, PERSON, recall, exact: 0.00
patterns, PERSON, recall, overlap: 0.00
patterns, PHONE_NUMBER, recall, exact: 0.84
patterns, PHONE_NUMBER, recall, overlap: 0.85
patterns, precision, exact: 0.97
patterns, texts with every labelled span masked: 405 of 2,586
model, detections: 4,424
model, CREDIT_CARD, recall, exact: 0.69
model, CREDIT_CARD, recall, overlap: 0.69
model, DATE_TIME, recall, exact: 0.97
model, DATE_TIME, recall, overlap: 0.97
model, EMAIL_ADDRESS, recall, exact: 1.00
model, EMAIL_ADDRESS, recall, overlap: 1.00
model, IBAN_CODE, recall, exact: 0.99
model, IBAN_CODE, recall, overlap: 1.00
model, LOCATION, recall, exact: 0.67
model, LOCATION, recall, overlap: 0.79
model, PERSON, recall, exact: 0.84
model, PERSON, recall, overlap: 0.84
model, PHONE_NUMBER, recall, exact: 0.94
model, PHONE_NUMBER, recall, overlap: 0.94
model, precision, exact: 0.84
model, texts with every labelled span masked: 2,095 of 2,586
both, detections: 5,963
both, CREDIT_CARD, recall, exact: 0.92
both, CREDIT_CARD, recall, overlap: 0.92
both, DATE_TIME, recall, exact: 1.00
both, DATE_TIME, recall, overlap: 1.00
both, EMAIL_ADDRESS, recall, exact: 1.00
both, EMAIL_ADDRESS, recall, overlap: 1.00
both, IBAN_CODE, recall, exact: 1.00
both, IBAN_CODE, recall, overlap: 1.00
both, LOCATION, recall, exact: 0.67
both, LOCATION, recall, overlap: 0.79
both, PERSON, recall, exact: 0.84
both, PERSON, recall, overlap: 0.84
both, PHONE_NUMBER, recall, exact: 0.99
both, PHONE_NUMBER, recall, overlap: 0.99
both, precision, exact: 0.88
both, texts with every labelled span masked: 2,120 of 2,586
model, account_number, detections: 746
model, account_number, precision, exact: 0.51
model, account_number, precision, overlap: 0.51
model, private_address, detections: 177
model, private_address, precision, exact: 0.79
model, private_address, precision, overlap: 1.00
model, private_date, detections: 384
model, private_date, precision, exact: 0.50
model, private_date, precision, overlap: 0.50
model, private_email, detections: 543
model, private_email, precision, exact: 1.00
model, private_email, precision, overlap: 1.00
model, private_person, detections: 2,110
model, private_person, precision, exact: 0.98
model, private_person, precision, overlap: 0.98
model, private_phone, detections: 464
model, private_phone, precision, exact: 0.89
model, private_phone, precision, overlap: 0.89
| Measure | Patterns | Model | Both |
|---|---|---|---|
Recall, exact, PERSON |
0.00 | 0.84 | 0.84 |
Recall, exact, LOCATION |
0.00 | 0.67 | 0.67 |
Recall, exact, PHONE_NUMBER |
0.84 | 0.94 | 0.99 |
Recall, exact, CREDIT_CARD |
0.71 | 0.69 | 0.92 |
Recall, exact, IBAN_CODE |
1.00 | 0.99 | 1.00 |
| Precision, exact | 0.97 | 0.84 | 0.88 |
| Texts fully masked | 405 of 2,586 | 2,095 of 2,586 | 2,120 of 2,586 |
The model finds most of the names and addresses the patterns can't, and the two detectors complement each other on card numbers. The model and the patterns find about the same share of cards, 0.69 and 0.71, but not the same cards, so together they find 0.92. A later section shows why the model's share is low.
The model pays in precision, 0.84 overall, and only 0.51 for account_number and 0.50 for private_date. That partly measures a difference in label policy. The truth leaves invoice numbers and dates of a problem unlabelled, and OpenAI's card says appropriate label policies can differ (section 4.2).
Together, the two detectors leave 2,120 of 2,586 texts with nothing personal in them, against 405 of 2,586 for the patterns alone.
この部分はまだ翻訳されていないため、英語で表示している。
Read the model's misses
OpenAI's card says where the model fails: it misses rare names, names from other naming traditions, initials, names wrapped in titles and domain-specific identifiers, and it over-masks public entities, locations and common nouns when the local context is unclear (OpenAI, 2026, section 4.3). Check that list against the hard cases the tickets plant:
1"""Counts how many of each hard case the model's recorded spans catch, and reads the names it misses by case and length.2The prose rests on the missed-name counts and on the first lowercase ticket that both detectors miss."""3from collections import Counter45from lib import pii67model, _ = pii.recorded("pii-entities")8labelled = pii.truth()9cases = pii.hard_cases(labelled)1011for case, spans in cases.items():12 print(f"{case}, labelled: {len(spans)}")13 print(f"{case}, caught by the model: {pii.caught(spans, model)}")14for kind, spans in pii.lookalikes().items():15 print(f"{kind}, flagged by the model: {pii.caught(spans, model)}")1617# The names the model misses, by case: read them before trusting a recall figure.18missed = pii.missed([s for s in labelled if s.entity == "PERSON"], model, {"private_person"})19print("names the model misses:", len(missed))20for case in ("first names that are words", "instructors named in reviews"):21 often = Counter(pii.text_of(s) for s in pii.missed(cases[case], model, {"private_person"})).most_common(3)22 print(f"{case}, missed most often:", ", ".join(name for name, _ in often))2324# A first name on its own says less than a full name: how many of the misses are one word?25print("missed names that are one word:", sum(len(pii.text_of(s).split()) == 1 for s in missed))26print("missed names of two words or more:", sum(len(pii.text_of(s).split()) > 1 for s in missed))27# islower() counts only names typed entirely in lowercase, so a name with a capital letter, such as "Jane", doesn't.28print("of them, typed in lowercase:", sum(len(pii.text_of(s).split()) > 1 and pii.text_of(s).islower() for s in missed))2930# A lowercase name that neither the model nor the platform's patterns cover any part of, in the first ticket with one.31# The model's spans and the patterns' together: a name is missed only when both miss it. The lowest ticket ID is taken,32# so the same ticket is printed on every run.33first = min(pii.missed(cases["names in lowercase"], model + pii.find(pii.platform_detector())), key=lambda s: s.row_id)34print("first ticket with a lowercase name both detectors miss:", first.row_id)35print("the name, as typed:", pii.text_of(first))
python privacy-filter-hard-cases.pynames in lowercase, labelled: 211
names in lowercase, caught by the model: 167
initial and surname, labelled: 163
initial and surname, caught by the model: 162
first names that are words, labelled: 187
first names that are words, caught by the model: 128
instructors named in reviews, labelled: 798
instructors named in reviews, caught by the model: 535
phones typed as digits only, labelled: 257
phones typed as digits only, caught by the model: 256
invoice numbers, flagged by the model: 224
order numbers, flagged by the model: 125
dates of a problem, flagged by the model: 188
names the model misses: 387
first names that are words, missed most often: Summer, Will, Hope
instructors named in reviews, missed most often: Marie, Lori, Augustin
missed names that are one word: 337
missed names of two words or more: 50
of them, typed in lowercase: 43
first ticket with a lowercase name both detectors miss: 19
the name, as typed: juan fonseca
The misses are first names that are also words, and an instructor's first name alone in a review. The model catches 128 of the 187 first names that are words, and 535 of the 798 instructors' names.
Initials aren't the problem: the model catches 162 of 163 initials with a surname, and lowercase names are mostly caught, 167 of 211.
Most often it misses the words Summer, Will, Hope and the instructors' names Marie, Lori, Augustin. The model also flags far more look-alikes than the tuned patterns: 224 invoice numbers, 125 order numbers and 188 dates of a problem, against 31, 0 and 0.
How much the misses matter depends on their length. Of the 387 names the model misses, 337 are a single word, a first name on its own, and 50 are longer, 43 of those typed in lowercase. The authors of the Text Anonymization Benchmark draw the same distinction: missing a direct identifier, such as a full name, is much more harmful than missing a quasi-identifier (Pilán et al., 2022). A first name alone still needs masking, since a review carries its learner's ID, and an instructor's first name in a review of their own course points at one person.
The card recommends testing the model in your own domain against local policy references before production use (section 4.5). It also lists education among the settings that need extra caution (section 4.4), and calls the model "a redaction and data minimization aid, not an anonymization, compliance, or a safety guarantee" (section 4.1).
Working rule: Mask free text with a PII model and the tuned patterns together, whatever either finds: the model for names and addresses, the patterns' checksums for card numbers and IBANs. Record the model's output with its revision, weights and operating point pinned, keep its own labels, and map them in code. Measure it on your own text, by hard case, before use and after every model change; if it misses too much, try an operating point that leans toward recall and record again. Treat masked text as reduced, never as anonymous.
この部分はまだ翻訳されていないため、英語で表示している。
Count what a wrong label costs
The comparison with the patterns scored the model by exact and overlap matching, which both need a label of the span's type. Masking doesn't read the label: a card number the model labels private_phone is still hidden. Classification does, because governance/pii.toml maps each entity type to a classification: a phone number to personal, a card number to sensitive. Measure the model's coverage beside its recall, and the labels it gives the platform's card numbers, phone numbers and addresses:
1"""Measures the model's coverage of card numbers, phone numbers and addresses whatever their label, and counts the labels2that would misclassify them. The prose rests on the coverage lines, the mislabelled counts and the uncovered addresses."""3from lib import pii45# What the model's labels cost. A span is covered when every character of it is inside some detection, whatever its6# label: that's what masking needs. Exact and overlap matching also need a label of the span's type.7model, _ = pii.recorded("pii-entities")8labelled = pii.truth()9covered = pii.coverage(model, labelled)10for entity in ("CREDIT_CARD", "PHONE_NUMBER", "LOCATION"):11 n, fully = covered[entity]12 print(f"{entity}, covered by the model, any label: {fully / n:.2f}")1314spans = {entity: [s for s in labelled if s.entity == entity] for entity in ("CREDIT_CARD", "PHONE_NUMBER", "LOCATION")}15print("card numbers labelled private_phone:", pii.caught(spans["CREDIT_CARD"], model, {"private_phone"}))16print("phone numbers labelled account_number:", pii.caught(spans["PHONE_NUMBER"], model, {"account_number"}))1718# For each address, the labels of the detections that overlap it, and the characters no detection covers.19on = pii.labels_on(spans["LOCATION"], model)20print("addresses with no detection at all:", sum(not labels for labels in on))21print("addresses read, at least in part, as a person:", sum("private_person" in labels for labels in on))22# A person label and no address label: the address was read as a name, which overlap matching can't credit.23print("of them, with no address label:", sum({"private_person"} <= labels and "private_address" not in labels for labels in on))24left = [pii.uncovered(address, model) for address in spans["LOCATION"]]25print("addresses not fully covered:", sum(bool(chars) for chars in left))26print("of them, with only spaces and punctuation left:", sum(bool(chars) and not any(c.isalnum() for c in chars) for chars in left))
python privacy-filter-labels.pyCREDIT_CARD, covered by the model, any label: 0.87
PHONE_NUMBER, covered by the model, any label: 1.00
LOCATION, covered by the model, any label: 0.67
card numbers labelled private_phone: 40
phone numbers labelled account_number: 27
addresses with no detection at all: 24
addresses read, at least in part, as a person: 28
of them, with no address label: 20
addresses not fully covered: 70
of them, with only spaces and punctuation left: 21
A wrong label costs classification more than it costs masking. The model covers 0.87 of card numbers, but labels 40 of the 213 as phone numbers, so its recall for cards is only 0.69. If the platform classified columns from the model's labels, a column of those card numbers would be proposed personal, not sensitive. That's what the patterns add: their Luhn check keeps card numbers labelled as cards.
The mistake also runs the other way, toward the stricter side. The model labels 27 phone numbers account_number, which maps to card numbers and IBANs, so its phone coverage is 1.00 and its recall 0.94.
Addresses show what each measure counts. The model's exact recall for them is 0.67 and its overlap recall 0.79, and its coverage is 0.67. The model finds nothing at all in 24 addresses.
The model reads part of 28 addresses as a person, since Faker builds many street names from surnames, as the platform's data card notes. It gives 20 of those no address label at all, so overlap matching misses them too. Other addresses come back in pieces with the right label, such as a street and a town split at a comma. Overlap matching credits those, and coverage doesn't. Of the 70 addresses not fully covered, 21 have every letter and digit masked and only a comma or a space left. Coverage is the measure masking needs, and it's strict.
Working rule: Report coverage, whatever the label, beside recall with the right label: masking needs the first, classification the second. Read which labels a detector gives each type of span, and keep a recognizer with a checksum for every identifier whose label decides a classification, such as card numbers.
この部分はまだ翻訳されていないため、英語で表示している。
Classify again when the schema changes
A classification describes a column at one moment, and chapter 2 showed how schemas move under it. So the question is when to classify again, not on every schema ID: in PyIceberg, editing a column's description gives the schema a new ID with no new column. What needs classifying is a field ID, the number Iceberg gives each column, that the metadata has never seen. Iceberg gives every added column a new one, and a renamed column keeps its ID and so its reviewed classification. Values can also change without a schema change, so the samples of text columns need a rerun on a schedule too. Vendors promise this as a service: Databricks says its classification scans incrementally and classifies new data with no manual setup (Databricks docs), a claim we don't test.
The support team wants a number to call learners back on for tickets opened by phone, so it adds a column called callback_number to support.tickets. The change comes in four steps: edit a description, add the column, fill it from the learners' phone numbers, then classify only the field IDs that governance/metadata.toml lacks:
1"""Edits the tickets table twice, first a column's description and then a new column, and after each change counts the field2IDs the metadata lacks. The prose rests on the schema IDs, the field counts and the proposal for the new column."""3from pyiceberg.types import StringType45from lib import metadata, pii6from lib.catalog import fill_column, open_catalog7from lib.platform import load8from lib.warehouse import connect910catalog = open_catalog(["support.tickets"])11tickets = catalog.load_table("support.tickets")12reviewed = metadata.load()["support.tickets"].columns # field ID -> the column as people reviewed it13# A field ID the reviewed metadata doesn't have: Iceberg gives each added column a new one.14unclassified = lambda: {f.field_id for f in tickets.schema().fields if f.field_id not in reviewed}15print("schema ID at the start:", tickets.schema().schema_id)1617with tickets.update_schema() as update: # a doc edit: a new schema, no new column18 update.update_column("body", doc="What the learner wrote, as they wrote it.")19print("schema ID after a doc edit:", tickets.schema().schema_id)20print("fields to classify after the doc edit:", len(unclassified()))2122# The support team starts storing the number to call back for tickets opened by phone: the learner's phone number.23with tickets.update_schema() as update:24 update.add_column("callback_number", StringType(), doc="Where to call the learner back.")25phone_of = {row["learner_id"]: row["phone"] for row in load("crm.learners").to_pylist()}26# tickets from other channels have no callback number, so their value is None27fill_column(tickets, "callback_number", lambda row: phone_of[row["learner_id"]] if row["channel"] == "phone" else None)28print("schema ID after adding a column:", tickets.schema().schema_id)29print("fields to classify after adding a column:", len(unclassified()))3031# only= keeps the proposals to the field IDs the metadata lacks.32for f in pii.classify(catalog, connect(catalog), pii.platform_detector(), only={"support.tickets": unclassified()}):33 found = ", ".join(f"{entity} in {n} of {f.sampled}" for entity, n in f.found.items())34 print(f"{f.table}.{f.column}, field ID: {f.field_id}")35 print(f"{f.table}.{f.column}, entity its name suggests: {f.named}")36 print(f"{f.table}.{f.column}, found in its sampled values: {found}")37 print(f"{f.table}.{f.column}, proposed classification: {f.classification}")
python reclassify-new-columns.pyschema ID at the start: 0
schema ID after a doc edit: 1
fields to classify after the doc edit: 0
schema ID after adding a column: 2
fields to classify after adding a column: 1
support.tickets.callback_number, field ID: 9
support.tickets.callback_number, entity its name suggests: None
support.tickets.callback_number, found in its sampled values: PHONE_NUMBER in 154 of 173
support.tickets.callback_number, proposed classification: personal
A doc edit moves the schema to a new ID and leaves 0 fields to classify, since it adds no column. Adding the column moves the schema to 2, with 1 field to classify: field 9.
No name rule matches callback_number, since it contains none of the words the phone rule looks for, which is how a name rule misses a column nobody wrote it for. Its values settle it. The sample finds PHONE_NUMBER in 154 of 173, and the proposal is personal.
The pull request that adds the column is where its classification belongs, beside the metadata entry it needs: chapter 10 fails that pull request until the column has one. A proposal from values needs a column that holds values, so this one comes from the scheduled sample.
Working rule: Classify every field ID the metadata doesn't have, in the pull request that adds it, and don't let it merge without a reviewed classification. Key the trigger on field IDs, never on schema IDs. Sample every text column again on a schedule too, because values change without a schema change.
この部分はまだ翻訳されていないため、英語で表示している。
What goes wrong in production
A detector's worst failure is a miss, and its output always looks like a list of findings: what it misses never appears in it:
- Phone numbers read as bank numbers. With Presidio's defaults, every run of 8 to 17 digits is a US bank number, and so is every phone number typed without separators. The evidence for the ticket table lists 689 bank numbers that aren't there, a report of "bank numbers in tickets" sends someone to the wrong team, and mapping that entity to a classification would raise columns for the wrong reason. Keep only the recognizers your text needs, each with its own threshold, as the tuning section does, and count detections per label: a label with hundreds of hits and no labelled spans is a false positive.
- Names in free text missed. Patterns find no names, and the model misses some lowercase names, first names that are also words, and first names standing alone. Ticket 19 still says "this is juan fonseca, i still can't log in" after both detectors have run, and passes every check that counts detections. You notice only by measuring recall against labelled text, per hard case, and by reading a sample of masked output.
- Personal data in a column called
notes. No name rule marks it, and a reviewer who never read it classifies itinternal. Sample every text column's values, and treat free-text columns as personal until a sample says otherwise. - A column more sensitive than its metadata. Learners paste card numbers into tickets, so
support.tickets.bodyholdssensitivedata under apersonalclassification. Compare every proposal with the reviewed metadata, and route a stricter one to the table's owner. - A detector that reaches the network.
AnalyzerEngine()downloads a model, and tldextract fetches the Public Suffix List. Offline, the pipeline fails; online, the same text can be classified differently on two machines. A setting read at import holds only if it's made before anything imports the library. Configure the engine, pin what it would fetch, check that the setting held, and run the detector's tests with the network off. - Truth shaped by its generator. The platform's text comes from 30 sentence templates filled by Faker, which writes every date of birth one way, phone numbers that aren't valid where the learner lives, and street names built from people's names. Read the misses before trusting a recall figure, and measure again on labelled samples of your own text.
この部分はまだ翻訳されていないため、英語で表示している。
What this chapter decided
- Columns are classified from their name, their type and their values. Name rules run on every column; text columns are sampled; the strictest evidence wins, with
internalas the floor, and only a person setspublic. - Samples are reproducible: 200 non-null values per text column, by a seeded reservoir sample on one DuckDB thread.
- Presidio runs offline, on
NoOpNlpEngine, with 6 recognizers, each with its own threshold, phone regions read from the learners' countries, and tldextract's own copy of the Public Suffix List, checked whenlib.piiloads. - Detectors are measured against labelled spans: recall per entity type by exact and overlap matching with a label of the right type, coverage whatever the label, precision per label and texts left with nothing personal, with recall weighed first.
- A proposal stricter than the metadata is a finding:
support.tickets.bodygoes toteam-supportassensitive, andbilling.payments.card_numbertoteam-billing, with the evidence that it holds full card numbers. - Free text is masked with two detectors: OpenAI's Privacy Filter, recorded at a pinned revision and operating point, for names and addresses, and the tuned patterns for card numbers, IBANs and phone numbers, whose checksums keep card numbers labelled as cards. Masking hides whatever either finds; neither is trusted to make text anonymous.
- No example prints a whole phone number, card number or IBAN:
lib.pii.maskedkeeps the last four digits. - Reclassification follows field IDs: every field the metadata lacks is classified in the pull request that adds it, and text columns are sampled again on a schedule. A detector is only as good as the measurement behind it, and what it misses never appears in its output. The measurement is what tells a team which of its classifications it can rely on, and which it has to check by hand.
この版における本章
第2026.11.31版2026年11月19日時点で例が通過この章の11 例件のうち11件が合格
英語版の書籍(版2026.11.31)から翻訳した。