Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone
  1. Home
  2. Categories
  3. Uncategorized
  4. - Cominciare un'operazione di manutenzione- Ubriacarsi- Rompere tutto- Dare la colpa a Cloudflare

- Cominciare un'operazione di manutenzione- Ubriacarsi- Rompere tutto- Dare la colpa a Cloudflare

Uncategorized
2 2 6
Log in to reply

Feed RSS
- Cominciare un'operazione di manutenzione- Ubriacarsi- Rompere tutto- Dare la colpa a Cloudflare

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • alfa@nonoino.masto.hostundefined

    #FotoCheDavvero

    Uncategorized fotochedavvero
    3
    1
    0 Votes
    3 Posts
    1 Views
    alfa@nonoino.masto.hostundefined
    @GustavinoBevilacqua Si è fatta pure la scarpetta...
  • lasolitalaura_@sociale.networkundefined

    Questa casa è del 1600, quest’anno sono 80 anni che è entrata nelle nostre vita

    Uncategorized
    1
    1
    0 Votes
    1 Posts
    0 Views
    lasolitalaura_@sociale.networkundefined
    Questa casa è del 1600, quest’anno sono 80 anni che è entrata nella nostra vita.Mi domando quante donne prima di me, prima di mia madre e di mia nonna, siano state sedute davanti a questo camino a leggere un libro distratte da sogni, pensieri di amori infelici o semplicemente prese dal libro. Ce ne sono state molte ed è come se ci fosse un filo invisibile che ci unisce tutte.
  • oblomov@sociale.networkundefined

    «We're not in Kansas anymore» the trans person sighed in relief.

    Uncategorized kansas transgenocide fascism usa project2025 civilrights
    3
    0 Votes
    3 Posts
    2 Views
    oblomov@sociale.networkundefined
    Also I can't but read their URL asTCP/IP e-lineinstead of TC Pipeline, but that's probably just me and I don't know if it's intentional.
  • pogowasright@infosec.exchangeundefined

    Some folks may recall my anger on August 18 over a vendor who wasn't responding to alerts about exposing their clients' data.

    Uncategorized databreach dataleak incidentresponse incidentmanagement thirdparty vendor accountability
    1
    0 Votes
    1 Posts
    11 Views
    pogowasright@infosec.exchangeundefined
    Some folks may recall my anger on August 18 over a vendor who wasn't responding to alerts about exposing their clients' data. The data included court files or records that were confidential or even sealed. At the time, researchers had discovered two entities that were exposed. They subsequently discovered more.Yesterday, the vendor -- who had even ignored a call from the FBI -- finally secured one of the two after the client finally reached them on the phone. The vendor told them they had fixed the problem. But did they? [SPOILER ALERT: No.]You won't believe what happened next, or maybe you will, but you'll have to stay tuned for this story, which has now gotten astronomically bigger because not only were the data still not secured but the vendor -- after claiming that the researchers had used hacking techniques to access unsecured data -- inexplicably sent the client a list of ALL of vendor's clients with their technical details AND ALL OF THEIR LOGIN CREDENTIALS. [WTF!?]I have never been as tempted to issue an actual press release warning all entities about a specific vendor, but... wow. Stay tuned. Eventually, I will write this all up, but first, I want to hear what the client's lawyers and insurers decide to do to hold the vendor accountable.(August 18 post: https://infosec.exchange/deck/@PogoWasRight/115033245331860859)#databreach #dataleak #incidentresponse #incidentmanagement #thirdparty #vendor #accountability @zackwhittaker @aj_vicens @politico