# Its hilarious watching reporters tring to explain even the most basic database security concepts.

**URL:** <https://boards.straightdope.com/t/its-hilarious-watching-reporters-tring-to-explain-even-the-most-basic-database-security-concepts/740879>\
**Category:** Miscellaneous and Personal Stuff I Must Share\
**Created:** [December 19, 2015, 10:09pm UTC](https://boards.straightdope.com/t/its-hilarious-watching-reporters-tring-to-explain-even-the-most-basic-database-security-concepts/740879 "2015-12-19T22:09:16Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![aceplace57](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/aceplace57/32/3500_2.png) [@aceplace57](https://boards.straightdope.com/u/aceplace57)\
**Post date:** [December 19, 2015, 10:09pm UTC](https://boards.straightdope.com/t/its-hilarious-watching-reporters-tring-to-explain-even-the-most-basic-database-security-concepts/740879/1 "2015-12-19T22:09:16Z")

</div>

Where have the technical reporters gone? Reading the press’ attempt to explain the Hillary Clinton and Bernie Sanders data breach is both hilariously inept and painful.

Non technical people use databases all the time at their offices. They know the frustration of security denials. Getting multiple people to sign off on forms just so you can pull up a dept’s information on your screen. It’s been a part of our lives for decades.

Pull up a chair and lets see how this reporter tries to explain that somebody left full privileges on the databases’ user accounts.

What gibberish. Would it kill the reporter to explain . Security in a database? That individual users can only access data they’ve been given permission to read? An admin assistant in a dept can only access budget records for their department. They can’t see another dept’s budget and expenditures. That’s a very basic concept here. A big boss over the entire division might have an account with rights to see records for all the depts under him. But can’t see another division’s records.

It’s not a tech problem. Some dumb ass granted super privileges on these user accounts. Allowing them to see the entire database. Any DBA on the job for a week knows better than to do stupid shit like this.

You mean data is shared in a file? Why what in tarnation will these clever young people think of next? 😛 :smack: It’s called a database you idiot and they’ve been shared resources for at least 50 years.  
_which maintains a shared file of voter information for all of the party’s top presidential campaigns._

Really its a mountain out of a molehill. They left the door open and somebody walked in. Fix the account security, STFU, and move on. There’s nothing to see here other than the press exploiting a non-story.

> [@](#):
>
> At least one staffer working for Sen. Bernie Sanders (I-Vt.) has been punished for improperly accessing information from Hillary Clinton’s campaign following a technical foulup by the Democratic party’s data vendor that made each campaign’s data potentially accessible to its opponent. But both campaigns believe they have been wronged by the way the tech problem — and its aftermath — were handled.

> [@](#):
>
> The intrusion was reportedly the result of issues with software that a third-party contractor, NGP VAN, provided to the DNC, which maintains a shared file of voter information for all of the party’s top presidential campaigns.

---

<div class="post-metadata">

**Author:** ![TriPolar](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/tripolar/32/3008_2.png) [@TriPolar](https://boards.straightdope.com/u/TriPolar)\
**Post date:** [December 19, 2015, 10:26pm UTC](https://boards.straightdope.com/t/its-hilarious-watching-reporters-tring-to-explain-even-the-most-basic-database-security-concepts/740879/2 "2015-12-19T22:26:07Z")

</div>

It has been fun to watch. The whole story is just a political infight based on technical gibberish. To be fair, some of the talking heads know what they don’t understand, but do realize what most people do understand, and just say someone was accidently given privileges to see something they shouldn’t have.

---

<div class="post-metadata">

**Author:** ![aceplace57](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/aceplace57/32/3500_2.png) [@aceplace57](https://boards.straightdope.com/u/aceplace57)\
**Post date:** [December 19, 2015, 10:38pm UTC](https://boards.straightdope.com/t/its-hilarious-watching-reporters-tring-to-explain-even-the-most-basic-database-security-concepts/740879/3 "2015-12-19T22:38:37Z")

</div>

I am surprised a Sander’s staffer tried searching for Clinton records. Its like rattling a doorknob. You just expect it to be locked.

He may have been using a SQL query and it just dumped out.

Select \* From Voter\_Table will dump all records you have access too. Surprise, surprise you get more than you expected. Add a where statement (to narrow the search) and you just created a political scandal and lost your job all in one day.

---

<div class="post-metadata">

**Author:** ![JerrySTL](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@JerrySTL](https://boards.straightdope.com/u/JerrySTL)\
**Post date:** [December 20, 2015, 1:55am UTC](https://boards.straightdope.com/t/its-hilarious-watching-reporters-tring-to-explain-even-the-most-basic-database-security-concepts/740879/4 "2015-12-20T01:55:41Z")

</div>

I wonder if the database had proper profiles and privileges set up OR (drum roll please) the application was ‘handling’ the security stuff. As a DBA, I’ve seen all too often where the developer/programmer tries to reinvent the wheel instead of using the built-in capabilities of the database.

---

<div class="post-metadata">

**Author:** ![DorkVader](https://avatars.discourse-cdn.com/v4/letter/d/73ab20/32.png) [@DorkVader](https://boards.straightdope.com/u/DorkVader)\
**Post date:** [December 20, 2015, 2:09pm UTC](https://boards.straightdope.com/t/its-hilarious-watching-reporters-tring-to-explain-even-the-most-basic-database-security-concepts/740879/5 "2015-12-20T14:09:22Z")

</div>

nm

---

<div class="post-metadata">

**Author:** ![GrumpyBunny](https://avatars.discourse-cdn.com/v4/letter/g/bc8723/32.png) [@GrumpyBunny](https://boards.straightdope.com/u/GrumpyBunny)\
**Post date:** [December 20, 2015, 2:31pm UTC](https://boards.straightdope.com/t/its-hilarious-watching-reporters-tring-to-explain-even-the-most-basic-database-security-concepts/740879/6 "2015-12-20T14:31:15Z")

</div>

> [@aceplace57](#):
>
> I am surprised a Sander’s staffer tried searching for Clinton records. Its like rattling a doorknob. You just expect it to be locked.
> 
> He may have been using a SQL query and it just dumped out.
> 
> Select \* From Voter\_Table will dump all records you have access too. Surprise, surprise you get more than you expected. Add a where statement (to narrow the search) and you just created a political scandal and lost your job all in one day.

Yup, pretty easy to have happen. I had to run a similar SQL query a few weeks back, but luckily I don’t have READ ALL access and didn’t get every client’s data dumped into my drive. So I didn’t have to go to my boss and fall on my sword.

And I agree with the statements in this OP.

---

<div class="post-metadata">

**Author:** ![usedtobe](https://avatars.discourse-cdn.com/v4/letter/u/ec9cab/32.png) [@usedtobe](https://boards.straightdope.com/u/usedtobe)\
**Post date:** [December 21, 2015, 6:55am UTC](https://boards.straightdope.com/t/its-hilarious-watching-reporters-tring-to-explain-even-the-most-basic-database-security-concepts/740879/7 "2015-12-21T06:55:29Z")

</div>

The big problem (which we still see in the News!) is that _ **Programmers** _ can’t get database security straight.

Hey - if we make everything a GLOBAL variable, we don’t have to worry about proper linkages - everything will have access to every _thing!_.

Yep - and that’s the problem.

Everything you send to another machine is instantly accessible to anyone on it. With UPDATE authorization.  
We used to do code walk-throughs, and each program had to justify its database access.  
It might be time to consider the old-fashioned control table (to which only God ID’s could write).

Kids today!

---

<div class="post-metadata">

**Author:** ![Richard\_Pearse](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/richard_pearse/32/13144_2.png) [@Richard\_Pearse](https://boards.straightdope.com/u/Richard_Pearse)\
**Post date:** [December 21, 2015, 7:03am UTC](https://boards.straightdope.com/t/its-hilarious-watching-reporters-tring-to-explain-even-the-most-basic-database-security-concepts/740879/8 "2015-12-21T07:03:54Z")

</div>

I think everyone with expertise in some field has discovered that journalists know nothing about that field and aren’t willing to learn or make the slightest attempt at getting any details right. It doesn’t take long to realize that most journalists know nothing about _any_ field, including the art of writing a good news article.
