[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-G_lHoj8ix4wHDLA7cYNScFTKCcLpZZNkjLcTBn3Rsc8":3},{"data":4,"sourceMap":-1},{"info":5,"latest":20},{"_createdAt":6,"_id":7,"_rev":8,"_type":9,"_updatedAt":10,"avatar":11,"employee":16,"name":17,"slug":18},"2023-05-23T16:27:18Z","wp-author-173","9HpbCsT2tq0xwozQfkuDml","blogAuthor","2023-08-29T09:52:31Z",{"_type":12,"asset":13},"image",{"_ref":14,"_type":15},"image-98f9b95323bd3c23270590c62fe7cdc53a929730-1024x1024-jpg","reference","former","Dean Ward",{"current":19},"deanward",[21],{"_id":22,"author":23,"commentCount":29,"comments":30,"excerpt":31,"featureTag":27,"image":32,"publishedAt":35,"slug":36,"sponsored":27,"tags":38,"title":61},"wp-post-17261",[24],{"_id":7,"avatar":25,"name":17,"role":27,"slug":28},{"_type":12,"asset":26},{"_ref":14,"_type":15},null,{"current":19},0,false,"We take a detailed look at a hacking incident that gave a user unauthorized access to our code and data. ",{"_type":12,"asset":33},{"_ref":34,"_type":15},"image-268488385b0337d3415d1f0c141434086195d4f9-1200x630-png","2021-01-25T15:16:43.000Z",{"current":37},"a-deeper-dive-into-our-may-2019-security-incident",[39,47,52,57],{"_createdAt":40,"_id":41,"_rev":42,"_type":43,"_updatedAt":40,"slug":44,"title":46},"2023-05-23T16:43:21Z","wp-tagcat-company","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":45},"company","Company",{"_createdAt":40,"_id":48,"_rev":42,"_type":43,"_updatedAt":40,"slug":49,"title":51},"wp-tagcat-engineering",{"current":50},"engineering","Engineering",{"_createdAt":40,"_id":53,"_rev":42,"_type":43,"_updatedAt":40,"slug":54,"title":56},"wp-tagcat-legal",{"current":55},"legal","Legal",{"_createdAt":40,"_id":58,"_rev":42,"_type":43,"_updatedAt":40,"slug":59,"title":60},"wp-tagcat-security",{"current":60},"security","A deeper dive into our May 2019 security incident"]