Jay Beale

@jaybeale

CTO, SecurityAudit WG co-lead, 1st Linux lead, BastilleLinux, K8S Attack Trainer,

InGuardians Seattle
Vrijeme pridruživanja: siječanj 2008.

Medijski sadržaj

  1. 4. sij
    Odgovor korisnicima

    was thinking the same. With that said, seeing this PFSense developers post has made me wonder if I should wait before embracing WireGuard, but I’m newb there. What are your thoughts? Is WG’s advantage in LoC & modernity likely to give it better odds in vuln avoidance?

  2. 11. pro 2019.
    Odgovor korisniku/ci

    KubeCon's illness aftermath shouldn't be called Con-Flu, or even Kube-flu. More like KubeCon-Phage!

  3. 4. pro 2019.
    Odgovor korisnicima
  4. 4. pro 2019.

    Like, you were just talking about PyPi supply chain issues less than a week ago.

    Prikaži ovu nit
  5. 2. pro 2019.

    's talk can help keep physical penetration testers safe: "It is a service that involves a lot of emotional work..." Prepare your client for what you will do, communicate before, during and after. 1/n

    Prikaži ovu nit
  6. 2. pro 2019.

    's talk can help our field stay safe in doing penetration testing, esp physical, which is "a service that involves a lot of emotional work." & "Is that OK? Did we prepare them emotionally?"

    Prikaži ovu nit
  7. 20. stu 2019.

    Great meeting of (SIG-TopRopeClimbing) at Mesa Rim, 7 miles from - thanks ! I’m headed home in the morning, but people are going rock climbing tomorrow. ,

  8. 19. stu 2019.

    What a great 1st ! Sitting outside by the water, with , reminiscing about our hacking work together. They taught me so much about security and container multi-tenancy, before I'd ever touched Docker.

  9. 11. stu 2019.

    TIL: kubectl must be pronounced "cube control" - the CNCF's style guide for says ' version 1.9's Changelog locked this in (see image). Maybe this needs to be a less buried... I think I'm submitting a PR for the project website and docs.

    Prikaži ovu nit
  10. 9. stu 2019.
    Odgovor korisniku/ci

    I too believe that the two closest candidates for official pronunciations were "kube-control" and "kube-c-t-l". With that said, clearly just to mess with all of us, v1.1.14's release announcement introduced a new mascot for kubectl. It's called the ... kubee cuttle. (Nooooooo!)

  11. 8. stu 2019.

    '19 talks are up! In my talk, I demo'd hacking the Scott Pilgrim evil exes. Most proud of ex #3: attacking a microservice by MitMing its request to a 2nd microservice. I worked hard on this & hope you enjoy it! !

  12. 30. lis 2019.
    Odgovor korisniku/ci
  13. 25. lis 2019.

    API hacking conclusions

    Prikaži ovu nit
  14. 25. lis 2019.

    Nice findings continued: Portal refuses non-HTTPS, but the API accepts...

    Prikaži ovu nit
  15. 25. lis 2019.

    Account not bound by controls and can change those controls

    Prikaži ovu nit
  16. 25. lis 2019.

    started this morning hardcore, with API-hacking talk by , "I'm in your cloud: A year of hacking Azure AD." Awesome findings, incl. an "internal" API version that was available publicly. Access policies set via API, but invisible in the portal. Attack your APIs!

    Prikaži ovu nit
  17. 17. ruj 2019.

    Seattle started with a drum line!

  18. 3. ruj 2019.
    Odgovor korisniku/ci
  19. 8. kol 2019.

    Want to learn to hack clusters? Check out our new open source project, Bust-a-Kube, a multi-scenario intentionally-vulnerable, three node Kubernetes cluster. You can get it @ . More scenarios to come! If you're at , see me for a sticker!

  20. 8. kol 2019.

    Want to learn to hack clusters? Check out our new free project, Bust-a-Kube, an intentionally-vulnerable Kubernetes cluster. You can download it at . It has two scenarios in it, with more to come! If you're at , see me for a sticker!

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·