Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A.6 Roles and Responsibilities #2

Open
nelsonic opened this issue Dec 14, 2016 · 0 comments
Open

A.6 Roles and Responsibilities #2

nelsonic opened this issue Dec 14, 2016 · 0 comments

Comments

@nelsonic
Copy link
Member

What are the Roles and Responsibilities in our organisation?

So far I have:

### Management/Leadership team

The Management/Leadership team is ultimately responsible for the information
security in the organization; it is not "outsourced" to anyone else.

Day-to-day responsibility for checking that process/procedures for information
security are followed/met belongs to the data controller.

Data Controller

The Data Controller is the person in the organization who is registered/named
with the Information Commissioner's Office (UK) and responsible for
ensuring that
Data protection principles
are followed.

Application Developers

Application developers are responsible for implementing the code and systems
which have the protection of people's personal data at heart.

Additionally developers should make reasonable efforts to keep their
knowledge and skill current and keep track of security reports/advisories
which are relevant to the code which has been included/used in the application.

Developer Security Checklist

  1. Minimise the amount of sensitive Personally Identifiable Information (PII)
    stored by the application/database (e.g: if you don't need Social Security number don't ask for it!)
  2. Where PII is required for the functionality of the App, Encrypt as much as possible/practical.
  3. Never store PII in a session token (JWT) or localStorage (where it can be "stolen" by an "XSS" attack)
  4. Always use strong passwords for all systems & services.
  5. Always use multi-factor authentication for Gmail, GitHub & AWS to limit the risk of
    a malicious user gaining access to these mission-critical systems.

Under no circumstances should a developer merge her/his own change/feature/bugfix.

Quality Assurance

The Quality Assurance (QA) person (or team) is responsible for
checking/testing features of the application while they are being built
and before they are released to the "live" environment.
QA is the "gate keeper" between application developers and end-users.

QA should not write code unless the team is small and the QA/developer
role are being alternated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant