Digger scans your organisation’s file shares and finds the most sensitive data left in forgotten corners: passwords, secret keys, card and ID numbers. We plan a 2-hour session with you.
HIGH\\fs01\finance\2021\payments.xlsxCard number · Luhn ✓
HIGH\\fs01\hr\staff\list.csvTR ID number · validated
CRITICAL\\fs02\it\backup\server.ppkKey file · content not read
LOW\\fs01\shared\contacts.txtE-mail, mobile phone
Sample scan view
As shares grow, secrets get lost.
01
A config file copied years ago
A web.config left over from an old project may still carry the password of the live database.
02
Shared folders everyone can open
An export dropped into a shared folder may be full of card, IBAN or ID numbers.
03
Key files nobody remembers
Certificates, VPN profiles and password vaults can sit in folders nobody has opened in years.
Two hours to visible risk.
01
Plan
We plan a 2-hour session with you and agree on the file shares to scan.
02
Scan
Digger scans the shares and detects passwords, keys, card and identity data.
03
Prioritise
We go through the findings by severity with you, starting with the critical ones.
2
hours: one planned session
9
key file types reported without reading content
3
validation algorithms: Luhn, mod-97, TR ID
4
finding groups
What Digger detects.
Four groups of findings, each checked to keep false alarms down.
Passwords and secret keys
Critical
Password in a connection stringconnectionStringPassword=Pwd=
Password in config filesappSettings pairs such as the one below, and passwords in XML attributes.<add key="ApiKey" value="…">
Generic key/value pairsIncluding prefixed and suffixed variants.password=parola:şifre=secretapi_keytokenclient_secretMailPassworddb_pwd
Credentials embedded in URLshttps://user:password@server
Private keysPEM and OpenSSH headers.-----BEGIN … PRIVATE KEY-----
Cloud and developer tokensAWS access keys, Azure Storage and Service Bus keys, GitHub, GitLab and Slack tokens, JWT.
Financial
High
Credit and debit cardsChecked with the Luhn algorithm; test cards are filtered out.
CVV/CVC fieldsFields that hold card security codes.
TR IBANValidated with the mod-97 check.
Personal data
High
TR ID number (T.C. Kimlik No)Validated with the official algorithm.
Low severityE-mail addresses, Turkish mobile numbers and vehicle plates. A plate is reported only when words such as “plaka”, “araç” or “ruhsat” appear nearby.
Reported without reading content
By file type
Key and credential filesReported by file type, without opening the file..pfx.p12.jks.key.pem.ppk.kdbx.ovpn.rdg
The file name raises the stakes.
A “high” finding inside a high-risk file is automatically raised to “critical”.
web.configappsettings.json.envunattend.xml
HIGHCRITICAL
Validated findings, not noise.
Matches are checked before they reach the report, so your team spends its time on real risk.
Luhn check
Card numbers must pass the Luhn algorithm; known test cards are dropped.
mod-97
Turkish IBANs are validated with the mod-97 check.
Official TR ID algorithm
ID numbers are confirmed with the official check-digit algorithm.
Context check
Vehicle plates count only when plate, vehicle or licence words appear nearby.
A first step for KVKK and GDPR.
Knowing where personal data lives is the first step of a data inventory and risk assessment. Digger makes it visible in one planned session.
We use cookies to keep the site working, measure performance and improve your experience. Accept all, decline the extras, or choose what stays. Cookie Policy
Manage Your Cookies
Necessary cookies are always active. You can switch the other categories on or off at any time.
NecessaryAlways active
Required for core functions such as security, navigation and remembering your choices.
Analytics
Lets us measure anonymously which pages are useful and how the site is used.
Marketing
Used to show relevant content and campaigns on other platforms and measure their impact.
Preferences
Remembers choices such as language and layout to personalise your experience.
Planning a project or need a price? No chatbot here: our team answers you live.
Twinlike · Live chat
Real people, no bots. We usually reply within a few minutes.