language agnostic - Defining a security policy for a system -
most of literature on security talks importance of defining security policy before starting workout on mechanisms , implementation. while seems logical, quite unclear defining security policy means.
has here had experience in defining security policy, , if so:
1) outcome of such definition? form of such policy, distributed system, document containing series of statements on security requirements (what allowed , not) of system?
2) can policy take machine readable form (if makes sense) , if how can used?
3) how 1 maintain such policy? policy maintained documentation (as rest of documentation) on system?
4) is necessary make references policy document in code?
brian
you should take 1 of standard security policies , work there. 1 common pci compliance (payment card industry). it's thought out , except few soft spots, good. i've never heard of machine readable policy except microsoft active directory definition or series of linux iptables rules.
https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml
edit:
check out se linux policies also:
Comments
Post a Comment