#pii — Public Fediverse posts

Among the latest data-breach villains: the Washington Post

Members of the Washington Post’s extended diaspora, meaning both former employees as well as past freelancers, have begun getting an unwelcome reminder of that chapter in their professional lives: a letter from the Post, sent from an address not in the District but in West Sacramento, Calif., informing them of a “Data Security Incident.”

That inefficient phrase is defensive legalese for “data breach,” which the letter says, in comparably defensive passive voice, happened between July 10 and Aug. 22, 2025, when “certain data was accessed and acquired without authorization” from unspecified Oracle E-Business Suite applications.

In my case and others, to judge from reports from fellow recipients of this joyless notice, the “certain data” included names and Social Security numbers.

The letter may not spark any more joy at Oracle, since it describes the vulnerability exploited as a “previously unknown and widespread” flaw. Oracle’s own warning red-flags it as “remotely exploitable without authentication.” But the paper’s disclosure does not address another cause of the data breach: how the Post chose to retain this sort of sensitive data long after it should have stopped being regularly business-relevant.

Consider my example: The last time I had any ongoing transactions with the Post that should have involved my SSN was 15 years ago. I rolled over my 401(K) after leaving the paper, and Jeff Bezos buying the Post in 2013 resulted in the company transferring my pension and those of other ex-Posties to former publisher Don Graham’s firm Graham Holdings.

For the handful of freelance pieces I’ve sold to my old shop since then (such as the Jan. 28, 2019 opinion piece headlined “Big tech firms still don’t care about your privacy”), I’ve used the Employer Identification Number I obtained shortly after I started freelancing.

Yet apparently my SSN was still sitting unencrypted in a network-accessible database last summer, contrary to basic security advice, along with the digits of thousands of other current and former Post employees and contractors. Some had banking details compromised too.

That’s “thousands” as in 9,720 people, per a filing the Post made with Maine’s Attorney General in November that a few security publications covered at the time. A month later, a former Post employee named Jun Hee Kim filed a class-action lawsuit against the Post on behalf of those nearly 10,000 individuals.

I have yet to get a notice inviting me to join that class, and the Post’s letter does not mention the litigation. Instead, it offers the usual paltry remedy of a year of identity-theft monitoring, in this case from a firm called IDX.

I know that’s the standard act of apology not only from covering data breaches but from having my data exposed in them, over and over. I know the drill well enough to have turned “Equifax” into the verb “Equifaxed” and to have frozen my credit more than once.

So at some level, I’m not surprised at the news of the Post’s data breach so much as I’m surprised that it took this long. Throughout my time working at 15th and L, I saw the Post treat SSNs as carelessly as anybody else did decades ago–even using them as employee IDs, as seen in some of my own admin paperwork from early in this century showing the full nine digits. But it’s still stupid and sloppy that this particular data breach happened not in 2005 or 2015 but in 2025, well past the point when management at the Post should have known better.

Among the latest data-breach villains: the Washington Post

Members of the Washington Post’s extended diaspora, meaning both former employees as well as past freelancers, have begun getting an unwelcome reminder of that chapter in their professional lives: a letter from the Post, sent from an address not in the District but in West Sacramento, Calif., informing them of a “Data Security Incident.”

That inefficient phrase is defensive legalese for “data breach,” which the letter says, in comparably defensive passive voice, happened between July 10 and Aug. 22, 2025, when “certain data was accessed and acquired without authorization” from unspecified Oracle E-Business Suite applications.

In my case and others, to judge from reports from fellow recipients of this joyless notice, the “certain data” included names and Social Security numbers.

The letter may not spark any more joy at Oracle, since it describes the vulnerability exploited as a “previously unknown and widespread” flaw. Oracle’s own warning red-flags it as “remotely exploitable without authentication.” But the paper’s disclosure does not address another cause of the data breach: how the Post chose to retain this sort of sensitive data long after it should have stopped being regularly business-relevant.

Consider my example: The last time I had any ongoing transactions with the Post that should have involved my SSN was 15 years ago. I rolled over my 401(K) after leaving the paper, and Jeff Bezos buying the Post in 2013 resulted in the company transferring my pension and those of other ex-Posties to former publisher Don Graham’s firm Graham Holdings.

For the handful of freelance pieces I’ve sold to my old shop since then (such as the Jan. 28, 2019 opinion piece headlined “Big tech firms still don’t care about your privacy”), I’ve used the Employer Identification Number I obtained shortly after I started freelancing.

Yet apparently my SSN was still sitting unencrypted in a network-accessible database last summer, contrary to basic security advice, along with the digits of thousands of other current and former Post employees and contractors. Some had banking details compromised too.

That’s “thousands” as in 9,720 people, per a filing the Post made with Maine’s Attorney General in November that a few security publications covered at the time. A month later, a former Post employee named Jun Hee Kim filed a class-action lawsuit against the Post on behalf of those nearly 10,000 individuals.

I have yet to get a notice inviting me to join that class, and the Post’s letter does not mention the litigation. Instead, it offers the usual paltry remedy of a year of identity-theft monitoring, in this case from a firm called IDX.

I know that’s the standard act of apology not only from covering data breaches but from having my data exposed in them, over and over. I know the drill well enough to have turned “Equifax” into the verb “Equifaxed” and to have frozen my credit more than once.

So at some level, I’m not surprised at the news of the Post’s data breach so much as I’m surprised that it took this long. Throughout my time working at 15th and L, I saw the Post treat SSNs as carelessly as anybody else did decades ago–even using them as employee IDs, as seen in some of my own admin paperwork from early in this century showing the full nine digits. But it’s still stupid and sloppy that this particular data breach happened not in 2005 or 2015 but in 2025, well past the point when management at the Post should have known better.

Among the latest data-breach villains: the Washington Post

Members of the Washington Post’s extended diaspora, meaning both former employees as well as past freelancers, have begun getting an unwelcome reminder of that chapter in their professional lives: a letter from the Post, sent from an address not in the District but in West Sacramento, Calif., informing them of a “Data Security Incident.”

That inefficient phrase is defensive legalese for “data breach,” which the letter says, in comparably defensive passive voice, happened between July 10 and Aug. 22, 2025, when “certain data was accessed and acquired without authorization” from unspecified Oracle E-Business Suite applications.

In my case and others, to judge from reports from fellow recipients of this joyless notice, the “certain data” included names and Social Security numbers.

The letter may not spark any more joy at Oracle, since it describes the vulnerability exploited as a “previously unknown and widespread” flaw. Oracle’s own warning red-flags it as “remotely exploitable without authentication.” But the paper’s disclosure does not address another cause of the data breach: how the Post chose to retain this sort of sensitive data long after it should have stopped being regularly business-relevant.

Consider my example: The last time I had any ongoing transactions with the Post that should have involved my SSN was 15 years ago. I rolled over my 401(K) after leaving the paper, and Jeff Bezos buying the Post in 2013 resulted in the company transferring my pension and those of other ex-Posties to former publisher Don Graham’s firm Graham Holdings.

For the handful of freelance pieces I’ve sold to my old shop since then (such as the Jan. 28, 2019 opinion piece headlined “Big tech firms still don’t care about your privacy”), I’ve used the Employer Identification Number I obtained shortly after I started freelancing.

Yet apparently my SSN was still sitting unencrypted in a network-accessible database last summer, contrary to basic security advice, along with the digits of thousands of other current and former Post employees and contractors. Some had banking details compromised too.

That’s “thousands” as in 9,720 people, per a filing the Post made with Maine’s Attorney General in November that a few security publications covered at the time. A month later, a former Post employee named Jun Hee Kim filed a class-action lawsuit against the Post on behalf of those nearly 10,000 individuals.

I have yet to get a notice inviting me to join that class, and the Post’s letter does not mention the litigation. Instead, it offers the usual paltry remedy of a year of identity-theft monitoring, in this case from a firm called IDX.

I know that’s the standard act of apology not only from covering data breaches but from having my data exposed in them, over and over. I know the drill well enough to have turned “Equifax” into the verb “Equifaxed” and to have frozen my credit more than once.

So at some level, I’m not surprised at the news of the Post’s data breach so much as I’m surprised that it took this long. Throughout my time working at 15th and L, I saw the Post treat SSNs as carelessly as anybody else did decades ago–even using them as employee IDs, as seen in some of my own admin paperwork from early in this century showing the full nine digits. But it’s still stupid and sloppy that this particular data breach happened not in 2005 or 2015 but in 2025, well past the point when management at the Post should have known better.

Among the latest data-breach villains: the Washington Post

Members of the Washington Post’s extended diaspora, meaning both former employees as well as past freelancers, have begun getting an unwelcome reminder of that chapter in their professional lives: a letter from the Post, sent from an address not in the District but in West Sacramento, Calif., informing them of a “Data Security Incident.”

That inefficient phrase is defensive legalese for “data breach,” which the letter says, in comparably defensive passive voice, happened between July 10 and Aug. 22, 2025, when “certain data was accessed and acquired without authorization” from unspecified Oracle E-Business Suite applications.

In my case and others, to judge from reports from fellow recipients of this joyless notice, the “certain data” included names and Social Security numbers.

The letter may not spark any more joy at Oracle, since it describes the vulnerability exploited as a “previously unknown and widespread” flaw. Oracle’s own warning red-flags it as “remotely exploitable without authentication.” But the paper’s disclosure does not address another cause of the data breach: how the Post chose to retain this sort of sensitive data long after it should have stopped being regularly business-relevant.

Consider my example: The last time I had any ongoing transactions with the Post that should have involved my SSN was 15 years ago. I rolled over my 401(K) after leaving the paper, and Jeff Bezos buying the Post in 2013 resulted in the company transferring my pension and those of other ex-Posties to former publisher Don Graham’s firm Graham Holdings.

For the handful of freelance pieces I’ve sold to my old shop since then (such as the Jan. 28, 2019 opinion piece headlined “Big tech firms still don’t care about your privacy”), I’ve used the Employer Identification Number I obtained shortly after I started freelancing.

Yet apparently my SSN was still sitting unencrypted in a network-accessible database last summer, contrary to basic security advice, along with the digits of thousands of other current and former Post employees and contractors. Some had banking details compromised too.

That’s “thousands” as in 9,720 people, per a filing the Post made with Maine’s Attorney General in November that a few security publications covered at the time. A month later, a former Post employee named Jun Hee Kim filed a class-action lawsuit against the Post on behalf of those nearly 10,000 individuals.

I have yet to get a notice inviting me to join that class, and the Post’s letter does not mention the litigation. Instead, it offers the usual paltry remedy of a year of identity-theft monitoring, in this case from a firm called IDX.

I know that’s the standard act of apology not only from covering data breaches but from having my data exposed in them, over and over. I know the drill well enough to have turned “Equifax” into the verb “Equifaxed” and to have frozen my credit more than once.

So at some level, I’m not surprised at the news of the Post’s data breach so much as I’m surprised that it took this long. Throughout my time working at 15th and L, I saw the Post treat SSNs as carelessly as anybody else did decades ago–even using them as employee IDs, as seen in some of my own admin paperwork from early in this century showing the full nine digits. But it’s still stupid and sloppy that this particular data breach happened not in 2005 or 2015 but in 2025, well past the point when management at the Post should have known better.

DATE: June 24, 2026 at 04:05PM
SOURCE: HEALTHCARE INFO SECURITY

Direct article link at end of text block below.

#Stryker Seeks to Dismiss Class Action Lawsuit in #Cyberattack https://t.co/7OeJOMmr6B #HIPAA #PII #PHI

Here are any URLs found in the article text:

https://t.co/7OeJOMmr6B

Articles can be found by scrolling down the page at https://www.healthcareinfosecurity.com/ under the title "Latest"

-------------------------------------------------

Private, vetted email list for mental health professionals: https://www.clinicians-exchange.org

Healthcare security & privacy posts not related to IT or infosec are at @HIPAABot . Even so, they mix in some infosec with the legal & regulatory information.

-------------------------------------------------

#security #healthcare #doctors #itsecurity #hacking #doxxing #psychotherapy #securitynews #psychotherapist #mentalhealth #psychiatry #hospital #socialwork #datasecurity #webbeacons #cookies #HIPAA #privacy #datanalytics #healthcaresecurity #healthitsecurity #patientrecords @infosec #telehealth #netneutrality #socialengineering

DATE: June 24, 2026 at 04:05PM
SOURCE: HEALTHCARE INFO SECURITY

Direct article link at end of text block below.

#Stryker Seeks to Dismiss Class Action Lawsuit in #Cyberattack https://t.co/7OeJOMmr6B #HIPAA #PII #PHI

Here are any URLs found in the article text:

https://t.co/7OeJOMmr6B

Articles can be found by scrolling down the page at https://www.healthcareinfosecurity.com/ under the title "Latest"

-------------------------------------------------

Private, vetted email list for mental health professionals: https://www.clinicians-exchange.org

Healthcare security & privacy posts not related to IT or infosec are at @HIPAABot . Even so, they mix in some infosec with the legal & regulatory information.

-------------------------------------------------

#security #healthcare #doctors #itsecurity #hacking #doxxing #psychotherapy #securitynews #psychotherapist #mentalhealth #psychiatry #hospital #socialwork #datasecurity #webbeacons #cookies #HIPAA #privacy #datanalytics #healthcaresecurity #healthitsecurity #patientrecords @infosec #telehealth #netneutrality #socialengineering

A Free Tool [DeFlock] Maps The License Plate Readers On Your Route [Flock, Etc], Then Lets You Slide Right Past Them
(Drivers can compare standard routes against camera-free alternatives with DeFlock’s growing surveillance database)
--
https://www.carscoops.com/2026/06/deflock-camera-avoidance-tool/ <-- shared technical media article
--
https://maps.deflock.org <-- shared (free) DeFlock webmap/resource
--
https://deflock.org/ <-- shared DeFlock overview web page, avoiding Flock Automated License Plate Readers
--
https://youtu.be/vU1-uiUlHTo?si=zXeNzwzf4IXi7BkL <-- shared YouTube video. “This Flock Camera Leak is like Netflix For Stalkers”, including lack of security and ready exposure of private & personal data
--
https://www.kunc.org/news/2026-06-19/fort-collins-drops-flock-surveillance-directs-data-collection-to-stop-and-cameras-to-be-removed <-- shared media article, example, City Of Fort Collins, CO dropping contract and getting Flock cameras removed
--
“…
• DeFlock can generate routes that avoid known [Automated License Plate Readers] ALPR cameras entirely.
• Users can choose how far they want to stay from surveillance cameras.
• The tool arrives as scrutiny of license plate readers continues to grow.
For years, automated license plate readers have quietly spread across America. They sit on utility poles, at intersections, near shopping centers, and along roads most drivers use every day. The overwhelming majority of motorists never notice them. A free website called DeFlock changes that by showing where many of those cameras are located and, more importantly, helping users avoid them if they choose. In a world where surveillance is often invisible, that’s a surprisingly powerful feature…”
--
“Automated License Plate Readers (ALPRs or LPRs) are AI-powered cameras that capture and analyze images of all passing vehicles, storing details like your car's location, date, and time. They also capture your car's make, model, colour, and identifying features such as dents, roof racks, and bumper stickers, often turning these into searchable data points.
These cameras collect data on millions of vehicles regardless of whether the driver is suspected of a crime. These systems are marketed as indispensable tools to fight crime, but they ignore the powerful tools police already have to track criminals, such as cell phone location data, creating a loophole that doesn't require a warrant…”
#DeFlock #PII #monitoring #automated #LicensePlateReaders #ALPR #LPR #cameras #avoid #camerafree #opendata # #invasionofprivacy #stalking #security #datasecurity #data #routing #webmap #free
#tracking #surveillance #surveillancestate #licenseplate #police #ICE #lawenforcement #warrantless #warrantlessSurveillance #warrantless_surveillance #flock #dystopia

A Free Tool [DeFlock] Maps The License Plate Readers On Your Route [Flock, Etc], Then Lets You Slide Right Past Them
(Drivers can compare standard routes against camera-free alternatives with DeFlock’s growing surveillance database)
--
https://www.carscoops.com/2026/06/deflock-camera-avoidance-tool/ <-- shared technical media article
--
https://maps.deflock.org <-- shared (free) DeFlock webmap/resource
--
https://deflock.org/ <-- shared DeFlock overview web page, avoiding Flock Automated License Plate Readers
--
https://youtu.be/vU1-uiUlHTo?si=zXeNzwzf4IXi7BkL <-- shared YouTube video. “This Flock Camera Leak is like Netflix For Stalkers”, including lack of security and ready exposure of private & personal data
--
https://www.kunc.org/news/2026-06-19/fort-collins-drops-flock-surveillance-directs-data-collection-to-stop-and-cameras-to-be-removed <-- shared media article, example, City Of Fort Collins, CO dropping contract and getting Flock cameras removed
--
“…
• DeFlock can generate routes that avoid known [Automated License Plate Readers] ALPR cameras entirely.
• Users can choose how far they want to stay from surveillance cameras.
• The tool arrives as scrutiny of license plate readers continues to grow.
For years, automated license plate readers have quietly spread across America. They sit on utility poles, at intersections, near shopping centers, and along roads most drivers use every day. The overwhelming majority of motorists never notice them. A free website called DeFlock changes that by showing where many of those cameras are located and, more importantly, helping users avoid them if they choose. In a world where surveillance is often invisible, that’s a surprisingly powerful feature…”
--
“Automated License Plate Readers (ALPRs or LPRs) are AI-powered cameras that capture and analyze images of all passing vehicles, storing details like your car's location, date, and time. They also capture your car's make, model, colour, and identifying features such as dents, roof racks, and bumper stickers, often turning these into searchable data points.
These cameras collect data on millions of vehicles regardless of whether the driver is suspected of a crime. These systems are marketed as indispensable tools to fight crime, but they ignore the powerful tools police already have to track criminals, such as cell phone location data, creating a loophole that doesn't require a warrant…”
#DeFlock #PII #monitoring #automated #LicensePlateReaders #ALPR #LPR #cameras #avoid #camerafree #opendata # #invasionofprivacy #stalking #security #datasecurity #data #routing #webmap #free
#tracking #surveillance #surveillancestate #licenseplate #police #ICE #lawenforcement #warrantless #warrantlessSurveillance #warrantless_surveillance #flock #dystopia

(8/n)

...#Twitter, #Musk already controls a huge part of the #Western #Narrative, not only on #SocialMedia.
Empowered by the #OrangePeril, he raided each and every #US government agency in 2025, while being in charge of #DOGE, in effect stealing secret #PII on most #US citizens. Having the #SocialSecurityNumber|s as well as the mail addresses, he is able to join all data, creating a utterly transparent human datapoint.
This is today.

Now image him controlling... @appassionato @mina @si_irini

GLiNER Guard (GLiGuard): один schema-driven энкодер вместо зоопарка LLM-гардрейлов

Деплоите LLM? Значит, обвешиваете её гардами. Сначала safety, потом PII, потом prompt injection, потом toxic BERT - и в один прекрасный день обнаруживаете, что у вас 5 классификаторов на каждой ноде и 20 forward-ов на один пользовательский запрос. GLiNER Guard (GLiGuard) - возможность схлопнуть этот стек в единый schema-driven энкодер. И да, его можно тоже промптить: через zero-shot + description.

https://habr.com/ru/companies/raft/articles/1037116/

#GLiNER_Guard #GLiGuard #GLiNER_2 #guardrails #PII #zeroshot #безопасность_LLM #обработка_ПД #модерация #schemadriven

Wisconsinites Can Keep Watching #Porn After Governor Vetoes #AgeVerification Bill

Evers wrote that the bill doesn’t prevent platforms from giving collected personal data to third parties, such as the government or #dataBrokers. “This is a violation of personal privacy,” he wrote.
#privacy #pii #security #wisconsin #veto

https://www.404media.co/wisconsin-age-verification-bill-vetoed/

Wisconsinites Can Keep Watching #Porn After Governor Vetoes #AgeVerification Bill

Evers wrote that the bill doesn’t prevent platforms from giving collected personal data to third parties, such as the government or #dataBrokers. “This is a violation of personal privacy,” he wrote.
#privacy #pii #security #wisconsin #veto

https://www.404media.co/wisconsin-age-verification-bill-vetoed/

JCB India Data Breach: 500k User Records Listed for Public Sale https://dailydarkweb.net/jcb-india-data-breach-500k-user-records-listed-for-public-sale/ #constructionequipment #Manufacturing #DataBreaches #customerdata #DatabaseSale #cyberattack #databreach #JCBIndia #India #JCB #PII

JCB India Data Breach: 500k User Records Listed for Public Sale https://dailydarkweb.net/jcb-india-data-breach-500k-user-records-listed-for-public-sale/ #constructionequipment #Manufacturing #DataBreaches #customerdata #DatabaseSale #cyberattack #databreach #JCBIndia #India #JCB #PII

Cargus Data Breach Exposes Over 550k Records https://dailydarkweb.net/cargus-data-breach-exposes-over-550k-records/ #DataBreaches #cyber-attack #databreach #CargusSRL #Logistics #datasale #Courier #Romania #Cargus #PII

AIPAC Discloses Data Breach, Says Hundreds Affected https://hackread.com/aipac-data-breach-hundreds-affected/ #Cybersecurity #CyberAttacks #HackingNews #CyberAttack #SupplyChain #databreach #Security #Privacy #Israel #AIPAC #PII #USA

AIPAC Discloses Data Breach, Says Hundreds Affected https://hackread.com/aipac-data-breach-hundreds-affected/ #Cybersecurity #CyberAttacks #HackingNews #CyberAttack #SupplyChain #databreach #Security #Privacy #Israel #AIPAC #PII #USA

Blavity Inc. Data Breach Exposes 1.2 Million Users https://dailydarkweb.net/blavity-inc-data-breach-exposes-1-2-million-users/ #DataBreaches #UnitedStates #BlavityInc #databreach #FulcrumSec #extortion #AfroTech #userdata #Blavity #media #PII

Blavity Inc. Data Breach Exposes 1.2 Million Users https://dailydarkweb.net/blavity-inc-data-breach-exposes-1-2-million-users/ #DataBreaches #UnitedStates #BlavityInc #databreach #FulcrumSec #extortion #AfroTech #userdata #Blavity #media #PII

Albanese Physical Therapy Data Breach Exposes Patient Records https://dailydarkweb.net/albanese-physical-therapy-data-breach-exposes-patient-records/ #AlbanesePhysicalTherapy #CyberSecurity #DataBreaches #Pennsylvania #UnitedStates #threatactor #databreach #Healthcare #datasale #PHI #PII

Albanese Physical Therapy Data Breach Exposes Patient Records https://dailydarkweb.net/albanese-physical-therapy-data-breach-exposes-patient-records/ #AlbanesePhysicalTherapy #CyberSecurity #DataBreaches #Pennsylvania #UnitedStates #threatactor #databreach #Healthcare #datasale #PHI #PII

Between 2022 and 2025, McKenzie Health System, which operates the McKenzie Memorial Hospital in rural Michigan, was hit by two major data breaches. Combined, the attacks compromised the personal and medical information of more than 79,000 patients.

https://www.suspectfile.com/two-data-breaches-in-three-years-the-mckenzie-health-system-case/

#AvosLocker #Data_Breach #McKenzie_Health_System #McKenzie_Memorial_Hospital #PHI #PII #Ransomware #Infosec

SNCF Connect Allegedly Breached, Millions of Customer and Worker Records for Sale https://dailydarkweb.net/sncf-connect-allegedly-breached-millions-of-customer-and-worker-records-for-sale/ #personallyidentifiableinformation #transportation #CyberSecurity #DataBreaches #databreach #dataleak #France #SNCF #PII

SNCF Connect Allegedly Breached, Millions of Customer and Worker Records for Sale https://dailydarkweb.net/sncf-connect-allegedly-breached-millions-of-customer-and-worker-records-for-sale/ #personallyidentifiableinformation #transportation #CyberSecurity #DataBreaches #databreach #dataleak #France #SNCF #PII

Indonesian Nuclear Energy Regulator BAPETEN Allegedly Breached https://dailydarkweb.net/indonesian-nuclear-energy-regulator-bapeten-allegedly-breached/ #NuclearIndustry #CyberSecurity #nuclearsafety #DataBreaches #databaseleak #databreach #government #Indonesia #BAPETEN #PII

Indonesian Nuclear Energy Regulator BAPETEN Allegedly Breached https://dailydarkweb.net/indonesian-nuclear-energy-regulator-bapeten-allegedly-breached/ #NuclearIndustry #CyberSecurity #nuclearsafety #DataBreaches #databaseleak #databreach #government #Indonesia #BAPETEN #PII

[Japan] Oster-Kollektion und mehr in Pokémon Centern

Der März bietet bisher viel neues Merchandise aus Japan.

Zur News: https://news.bisafans.de/11462

#Merchandise #Figuren #Japan #Ostern #Pikachu #Wablu #Altaria #Piepi #Sniebel #PokemonCenter #Psiana #Schmuck #Tragosso #Knuddeluff #Pii #Snubbull #Knogga #Wiesor #Wiesenior #Plüschfiguren #Felori #Flurmel

[Japan] Oster-Kollektion und mehr in Pokémon Centern

Der März bietet bisher viel neues Merchandise aus Japan.

Zur News: https://news.bisafans.de/11462

#Merchandise #Figuren #Japan #Ostern #Pikachu #Wablu #Altaria #Piepi #Sniebel #PokemonCenter #Psiana #Schmuck #Tragosso #Knuddeluff #Pii #Snubbull #Knogga #Wiesor #Wiesenior #Plüschfiguren #Felori #Flurmel

[Japan] Oster-Kollektion und mehr in Pokémon Centern

Der März bietet bisher viel neues Merchandise aus Japan.

Zur News: https://news.bisafans.de/11462

#Merchandise #Figuren #Japan #Ostern #Pikachu #Wablu #Altaria #Piepi #Sniebel #PokemonCenter #Psiana #Schmuck #Tragosso #Knuddeluff #Pii #Snubbull #Knogga #Wiesor #Wiesenior #Plüschfiguren #Felori #Flurmel

Data breach hitting PowerSchool looks very, very bad - Parents, students, teachers, and administrators throughout North America a... - https://arstechnica.com/security/2025/01/students-parents-and-teachers-still-smarting-from-breach-exposing-their-info/ #personallyidentifiableinformation #networkintrusions #databreach #security #biz⁢ #pii

Data breach hitting PowerSchool looks very, very bad - Parents, students, teachers, and administrators throughout North America a... - https://arstechnica.com/security/2025/01/students-parents-and-teachers-still-smarting-from-breach-exposing-their-info/ #personallyidentifiableinformation #networkintrusions #databreach #security #biz⁢ #pii

How to Protect Your Personal Info – Source:www.mcafee.com https://ciso2ciso.com/how-to-protect-your-personal-info-sourcewww-mcafee-com/ #howtoprotectpersonallyidentifiableinformation #McAfeeAntivirus|SecuringTomorrowRSSFeed #PersonallyIdentifiableInformation #McAfeeAntivirusSecuringTomorrow #Privacy&IdentityProtection #rssfeedpostgeneratorecho #HowToGuidesandTutorials #1CyberSecurityNewsPost #rssfeedsAutogenerated #CyberSecurityNews #McafeeSecurity #WhatisPII #Phishing #PII

How to Protect Your Personal Info – Source:www.mcafee.com https://ciso2ciso.com/how-to-protect-your-personal-info-sourcewww-mcafee-com/ #howtoprotectpersonallyidentifiableinformation #McAfeeAntivirus|SecuringTomorrowRSSFeed #PersonallyIdentifiableInformation #McAfeeAntivirusSecuringTomorrow #Privacy&IdentityProtection #rssfeedpostgeneratorecho #HowToGuidesandTutorials #1CyberSecurityNewsPost #rssfeedsAutogenerated #CyberSecurityNews #McafeeSecurity #WhatisPII #Phishing #PII

Dell warns of “incident” that may have leaked customers’ personal info - Enlarge (credit: Getty)

For years, Dell customers have been on... - https://arstechnica.com/?p=2023185 #personallyidentifiableinformation #security #breaches #biz⁢ #scams #dell #pii

Dell warns of “incident” that may have leaked customers’ personal info - Enlarge (credit: Getty)

For years, Dell customers have been on... - https://arstechnica.com/?p=2023185 #personallyidentifiableinformation #security #breaches #biz⁢ #scams #dell #pii

Hive ransomware apparently breached Intersport, a well known sporting goods company.

Lets see what this will bring, especially in the context of GDPR.

#HiveLeaks #Intersport #GDPR #PII

Hive ransomware apparently breached Intersport, a well known sporting goods company.

Lets see what this will bring, especially in the context of GDPR.

#HiveLeaks #Intersport #GDPR #PII

With it being #BlackFriday and all, I hope nobody is caught up in scams or phishing attacks while doing their (frantic!) online #shopping.

Here are a few #security and #privacy tips that I hope will help somebody:

1) If you have a coupon code, don't follow a provided link to the shopping page. Instead find the page yourself, e.g., via a #searchengine, and then input the coupon code manually.

2) Access online shops without being logged in, and without any #cookies, such that the shop cannot set prices according to #personaldata or previous purchases (yes, they do that). Except, of course, if the discount is only available when actually having an account. Attempt anonymously first.

3) An improvement to 2) is accessing online shops via #TorBrowser or similar.

4) Use a #VPN such that #ISPs and other adversaries cannot obtain or spoof information. It also protects your data, like credit card info, if you are using public a #WiFi (never do that without VPN).

5) As corollary to 4) you can even sometimes get discounts by using a different location than your own.

6) Use a #passwordmanager for your credentials such that they can be longer and harder to guess/crack. This also means you don't have to remember (or even know) them by heart.

7) Setup #MFA for your accounts such that, together with 6), it is harder for adversaries to break in and steal data and/or make automated purchases on your behalf if possible. It is highly advisable using an authenticator app instead of code-by-SMS. For further protection, you can even use #biometrics, like #fingerprints or facial scans. And/or a hardware device supporting #FIDO2/#U2F or similar.

Note that these tips are applicable also when not shopping, and I would encourage them all.

Stay safe and have an awesome Friday!

#mastodontips #feditips #profiling #personalidentifyinginformation #pii #internetserviceproviders #tor #multifactorauthentication #2fa #twofactorauthentication #yubikey

With it being #BlackFriday and all, I hope nobody is caught up in scams or phishing attacks while doing their (frantic!) online #shopping.

Here are a few #security and #privacy tips that I hope will help somebody:

1) If you have a coupon code, don't follow a provided link to the shopping page. Instead find the page yourself, e.g., via a #searchengine, and then input the coupon code manually.

2) Access online shops without being logged in, and without any #cookies, such that the shop cannot set prices according to #personaldata or previous purchases (yes, they do that). Except, of course, if the discount is only available when actually having an account. Attempt anonymously first.

3) An improvement to 2) is accessing online shops via #TorBrowser or similar.

4) Use a #VPN such that #ISPs and other adversaries cannot obtain or spoof information. It also protects your data, like credit card info, if you are using public a #WiFi (never do that without VPN).

5) As corollary to 4) you can even sometimes get discounts by using a different location than your own.

6) Use a #passwordmanager for your credentials such that they can be longer and harder to guess/crack. This also means you don't have to remember (or even know) them by heart.

7) Setup #MFA for your accounts such that, together with 6), it is harder for adversaries to break in and steal data and/or make automated purchases on your behalf if possible. It is highly advisable using an authenticator app instead of code-by-SMS. For further protection, you can even use #biometrics, like #fingerprints or facial scans. And/or a hardware device supporting #FIDO2/#U2F or similar.

Note that these tips are applicable also when not shopping, and I would encourage them all.

Stay safe and have an awesome Friday!

#mastodontips #feditips #profiling #personalidentifyinginformation #pii #internetserviceproviders #tor #multifactorauthentication #2fa #twofactorauthentication #yubikey

Apple’s AirDrop leaks users’ PII, and there’s not much they can do about it - Enlarge (credit: Apple)
AirDrop, the feature that allows Mac and iPhone users t... - https://arstechnica.com/?p=1759947 #personallyidentifiableinformation #airdrop #biz&it #policy #apple #tech #pii

Feds: former cloud worker hacks into Capital One and takes data for 106 million people - Enlarge (credit: Tdorante10)
A former systems engineer has been arrested on charges that she hack... more: https://arstechnica.com/?p=1543125 #personallyidentifiableinformation #hacking #biz&it #pii

@apLundell

and the last one: when your awkward personal #Data sneaks up on you:

https://mastodon.social/media/wnUgYRybNmsTnFKIR7c

https://mastodon.social/media/po1BqDp--Sg7z0dND_M

https://mastodon.social/media/zfvkxswuHdkUPiHfpJc

#PersonalData #PrivateData #PII #DataPuns #StarTrek