View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002233 | 10000-002: Security | public | 2012-10-23 15:48 | 2012-11-02 16:26 | |
Reporter | Paul Hunkar | Assigned To | Paul Hunkar | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Fixed in Version | 1.02 | ||||
Summary | 0002233: Security algorithm expiration | ||||
Description | From NIST security review the following suggestion has been made. Security algorithms typically have an expected lifetime, in that as computing power expands a security algorithm is expected to be able to e broken using a brute force method . The Specification should describe this idea and indicate that security policy will be updated. It may also be helpful if the standard reference some other document that describes this expected lifetime and /or make prediction on when security policies will expire. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
Added a refernce to NIST documentation that indicate the life time of security algorithm and also indicated that security policies expir and should be reviewed |
|
Reviewed and agreed to changes in 2012-10-30 telecon. |
Date Modified | Username | Field | Change |
---|---|---|---|
2012-10-23 15:48 | Paul Hunkar | New Issue | |
2012-10-23 18:29 | Jim Luth | Status | new => assigned |
2012-10-23 18:29 | Jim Luth | Assigned To | => Paul Hunkar |
2012-10-25 05:13 | Paul Hunkar | Status | assigned => resolved |
2012-10-25 05:13 | Paul Hunkar | Resolution | open => fixed |
2012-10-25 05:13 | Paul Hunkar | Note Added: 0004179 | |
2012-11-02 16:26 | Jim Luth | Status | resolved => closed |
2012-11-02 16:26 | Jim Luth | Note Added: 0004192 | |
2012-11-02 16:26 | Jim Luth | Fixed in Version | => 1.02 |