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

Security Policy [CORE3241] #3611

Open
firebird-automations opened this issue Nov 17, 2010 · 1 comment
Open

Security Policy [CORE3241] #3611

firebird-automations opened this issue Nov 17, 2010 · 1 comment

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Marcoci Dorin (marcodor)

Votes: 1

Decent DBMS should have Security Policies, something like is done in MS Active Directory.

Security Policy consist of a set of Policies: Password Security Policy, Account Security Policy, etc...

Policies define a set of rules rules that should be applied per server/database.

Password Policy include:
a. Password Expiration
b. Password Complexity
c. Minimum Password Length
d. etc...

Account Policy include
a. Account lockout settings (retries, time etc...)
b. etc...

Also woult be nice to apply diffirent set of policies to diffirent roles / security groups (for example accountants should change their password every month, other read only operators every year).

These requirements are present in recent database security standarts, and at least all major audit companies asks for it.

@firebird-automations
Copy link
Collaborator Author

Modified by: Marcoci Dorin (marcodor)

security: Developers [ 10012 ] =>

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