Expand GDPR Forum to Include Privacy

[CraginS]

Can we please change the name of the Discussions>GDPR forum to Privacy and GDPR?

Privacy protection is a core responsibility of our field, so much so that ISSA has partnered with IAPP to offer a free year of IAPP membership for ISSA members. Yet we have no obvious place in our forum set to start privacy-related threads that do not involve GDPR. No other action would be needed beyond the name change, but expanding the name will encourage members to place non-GDPR privacy items there.

Thank you.

Craig

[dcontesti]

Great suggestion.  I am currently working with some folks (from across Europe and NA) that are keen to keep abreast of Privacy and how it affects folks in Security.

We have published a couple of papers but as privacy laws continue to grow in leaps and bounds (CCPA has two new ones, New York is implementing, Nevada, etc) not to mention the laws coming out in places like New Zealand, Singapore, etc.

In very brief discussions with (ISC)2 they have stated they will publish our blogs, etc but so far want us to use Chapters and the Community to gather folks that are interested.  So if you are interested in more than GDPR let me know.

I am curious if there could be a Privacy Channel with sub sections to it?  Something like:

Privacy

 - GDPR

- CCPA

- NY Shield

That way folk could go to privacy and look at laws that may be specific to them.

We are open to thoughts and comments and people who are interested in helping.

@amandavanceISC2 @Jarred_LeFebvre @AndreaMoore Is it possible to nest topics and is it possible to at least rename GDPR as @CraginS has suggested?

d

[denbesten]

Personally, I would think removing "GDPR" altogether and using a name like "Privacy Regulations" or "Privacy Laws" would be more inline with the goal of "Internationalization".

On the other hand I generally use "Recent Activity" and Google to find things, so the forum's organizational structure is relatively unimportant to me. 

[rslade]

Since GDPR is just a bit of an expansion of the original privacy directives, I'm
surprised this is even an issue.

(On the other hand, it's yet another instance of Slade's Law of Computer History
[1] ...)





[1] - "Those do who not study Computer History are doomed to buy it again--
repackaged."

====================== (quote inserted randomly by Pegasus Mailer)
rslade@vcn.bc.ca slade@victoria.tc.ca rslade@computercrime.org
Great wits are sure to madness near allied. - John Dryden, 1681
victoria.tc.ca/techrev/rms.htm http://twitter.com/rslade
http://blogs.securiteam.com/index.php/archives/author/p1/
https://is.gd/RotlWB

[Kaity]

Thanks for tagging us in this! @AndreaMoore and I are looking into this!

[dcontesti]

---

@rslade wrote:
Since GDPR is just a bit of an expansion of the original privacy directives, I'm
surprised this is even an issue.

(On the other hand, it's yet another instance of Slade's Law of Computer History
[1] ...)




[1] - "Those do who not study Computer History are doomed to buy it again--
repackaged."

---

I have to agree.  Everything that is old becomes new again however as the laws keep coming at us, folks are not certain what steps to take, does it apply to them, how or do they have to change the way they work.....verbage changes between the laws or different words are used for the same thing

.Remember, not everyone is as old as you and I.........so they may not have danced around the mulberry bush to try to protect data and users PII.

I personally see some of the new (rewrites) privacy laws as ways of grabbing money (as some of the penalties are high) for governments, organizations, etc but unfortunately the security folk are the ones that have to ensure that the fines do not happen and that an organization is protected.

d