)]}'
{"security-guide/section_system-documentation-requirements.xml":[{"author":{"_account_id":2807,"name":"Bryan D. Payne","email":"bdpayne@acm.org","username":"bdpayne"},"change_message_id":"a51b642cbbe4db548bdf22a030a5703ead3c07d9","unresolved":false,"context_lines":[{"line_number":86,"context_line":"  \u003csection xml:id\u003d\"system-documentation-requirements-services-protocols-and-ports\"\u003e"},{"line_number":87,"context_line":"    \u003ctitle\u003eServices, protocols and ports\u003c/title\u003e"},{"line_number":88,"context_line":"    \u003cpara\u003eKnowing information about organizational assets is typically a best practice, therefore it is"},{"line_number":89,"context_line":"      beneficial to create a table which contains information regarding the service, protocols and ports being utilized in the OpenStack deployment. The table can be created from information derived from a CMDB or can be constructed manually and can be customized to include an overview of all services running within the cloud infrastructure. The level of detail contained in this type of table can be beneficial as the information can  immediately inform, guide, and assist with validating security requirements. Standard security components such as firewall configuration, service port conflicts, security remediation areas, and compliance become easier to maintain when concise information is available. An example of the aforementioned table is given below:\u003c/para\u003e"},{"line_number":90,"context_line":"    \u003cpara\u003e\u003cinlinemediaobject\u003e"},{"line_number":91,"context_line":"        \u003cimageobject role\u003d\"html\"\u003e"},{"line_number":92,"context_line":"          \u003cimagedata contentdepth\u003d\"166\" contentwidth\u003d\"967\""}],"source_content_type":"application/xml","patch_set":1,"id":"da86d52c_acba67bd","line":89,"updated":"2015-02-19 18:58:01.000000000","message":"I suggest a period after \"manually\".\n\nAlso please adjust the line length here to make the xml more readable.\n\nFinally, the last sentence can be simpler, perhaps just \"We show an example table below.\"?","commit_id":"d44d31f14d12fea20e447febc62b1e95abeac663"}]}