These "revelations" about leaks and vulnerabilities and screw-ups and just plain greedy lying people and businesses are not the exception, they are the rule.

If something needs to be private, keep it to yourself.

That is all.

Thank you for your time.

We’ve been living in this apartment now for almost a year. The coin fair laundry machines are in the basement, which is common area.

Since moving in, my fiancé has lost several pairs of underwear (mid-wash) and we have a sneaking suspicion on who it may be.

Before I go full spy mode, I’m going to ask a few of the families next to our unit if they have encountered a similar problem.

Reason I am reaching out to the security subreddit is to ask you, ladies and gentlemen; how would/should you go about catching this person? Are there any cost efficient, battery powered, motion activated small cameras I could hide in the laundry room? Let me know…

Thank You

EDIT: I appreciate the everybody’s input. It seems unfortunately that it is a bigger crime to catch the person doing the sex act than it is to actually commit it. If you cant beat them, join them. I will proceed by stealing peoples underwear as well until the entire building is plagued with this issue like we are. 🤦🏼‍♂️

I'm on the security engineering team at a SaaS company. Were couple hundred people. Spent part of last quarter building an automation pipeline: scanner finds a vuln, pipeline creates a Jira ticket with all the details, assigns it based on tags, pings the right Slack channel. Felt like a win. The manual ticket creation was eating hours every week.

So we launched it, it works perfectly. Tickets fly into Jira within minutes of a scan completing with a beautiful dashboard and everything automated end to end.

Except now I get to watch, in real time, as about 40 percent of those tickets land in unassigned and stay there.

The automation exposed what the manual process was hiding. When a human was creating tickets, theyd do the routing loop: check the CMDB, realize the owner field is stale, Slack someone who might know, eventually get it to the right person through sheer persistence. The automation cant do any of that. It reads the owner field. If the field says unassigned or points to a team that no longer exists or references someone who left, the ticket just sits there stuck.

So I automated the easy part. And now the hard part is actual ownership data, is the bottleneck and its more visible than ever. We didnt fix the routing problem. We just made it faster to surface.

Anyone else hit this? Any advice on how to fix the ownership mess?

Please I'm quite lost and panicky : I'm not 'advanced' in computer security and this is beyond my google skill, pls help :(

Here's the imgur link to what i have https://imgur.com/a/JDanRVa

Looking on indeed , all the job offers are for only 11-15$ an hour . How do people raise families on this salary ? Located in Illinois but looking for jobs in Kentucky or Tennessee

NO! i am not joking with just a sensational headline. This is crazy and this happened and you know what is crazier? the whole chunk of 22gb database is available publicly for anybody to download, literally anybody !
Get the drinks in your hand because the server which is hosting all that data is of china ..... DAMN !

The things started with the hacking and data breach of checkpeople(dot)com website  becasue the whole data belongs to this website . it is a people-finder company based in florida . source