Timeline for ISO 27001 and investigating production issues
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Feb 5, 2018 at 17:48 | history | suggested | Liath | CC BY-SA 3.0 | More tags, improved a few phrases and typos |
| Feb 5, 2018 at 15:56 | answer | added | k3b | timeline score: 0 | |
| Feb 5, 2018 at 11:56 | review | Suggested edits | |||
| S Feb 5, 2018 at 17:48 | |||||
| Feb 5, 2018 at 11:55 | answer | added | Liath | timeline score: 3 | |
| Feb 5, 2018 at 11:11 | comment | added | ntohl | @Mathematics Good logging also means customizable good logging. Narrow the field down where logging must be extended with extra information. Add some flags which switches between performance and lot of data. | |
| Feb 5, 2018 at 10:30 | comment | added | Mathematics | @ntohl I agree but it's not logging and we are trying to implement that but it doesn't helps with volume of data | |
| Feb 5, 2018 at 10:09 | comment | added | ntohl | That is why good logging is essential. You might work on an environment, where too realistic test-data is enough to inflict damage. For example XY's bank transactions. If You have good logging, than You might ask for the log's anonimized version, than work from that | |
| Feb 5, 2018 at 9:52 | comment | added | Pieter B | ISO 27001 also demands that test-data is realistic. | |
| Feb 5, 2018 at 9:29 | history | asked | Mathematics | CC BY-SA 3.0 |