Drupal is used for building sites and/or applications. These sites have a great variaty in location, purpose, use, etc. The owners of those sites are very diverse (individuals, organisations, governements, etc).
More and more we are facing an increase of laws, regulations, rules, guidelines, etc affecting some how those sites and/or the people or organisations behind those sites.
This working group is a platform where compliancy issues can be discussed in order provide positive solutions for the drupal community (developers and users).
In general, compliance means conforming to a rule, such as a specification, policy, standard or law. Regulatory compliance describes the goal that corporations or public agencies aspire to in their efforts to ensure that personnel are aware of and take steps to comply with relevant laws and regulations.
Due to the increasing number of regulations and need for operational transparency, organizations are increasingly adopting the use of consolidated and harmonized sets of compliance controls. This approach is used to ensure that all necessary governance requirements can be met without the unnecessary duplication of effort and activity from resources.
Drupal and FISMA Compliance BoF at Drupalcon LA
This session is for sharing of best practices and tools with respect to the FISMA federal compliance framework, as well as discussing ways to automate compliance checking of Drupal (and it's environment) using FISMA certified open source tools like OpenSCAP.
Read more
The EU's Data Protection Directive: Cookies
Discussion about The EU's Data Protection Directive and how to get drupal sites compliancy with this. Please provide your opinion on this matter.
Documentation
Actors
There are 2 direct/main actors;
- visitors
- site owners
There are several indirect actors on this:
- Developers
- third parties (advertisers, google analytics)
Related modules
<
table>
