Give Feedback (closed)
IT-ARCH Discussion List (closed)
Changes to the Security Architecture document
Leading to version 1.9.8, March 6, 2002
- Changed status to "Adopted by CIRT February 20, 2002".
Leading to version 1.9.7, September 19, 2001
- Changed status to "Ready for Adoption".
Leading to version 1.9.6, May 21, 2001
- In section 2, added "Configuration and Next Steps" to the document outline.
Leading to version 1.9.5, May 17, 2001
- Did copy editing to improve wording and fix formatting problems.
- Reordered and added entries to the tables in §6.4, 7.6 and 8.4 so they have the same technologies in the same order.
- Section 6.4: Added "Scripting tools," since that appears in Sections 7.6 and 8.4.
- Section 10:
- Changed heading to replace "Issues" with "Considerations".
- Added Directory Service consideration regarding its support for Security.
- Section 12:
- C-5: Added Implication #3 about need for a service.
- C-6, Reduce complexity: Added to Implications: interfaces, databases and directories.
- C-10: Listed implications from Doc 2 principle C.4.
Leading to version 1.9.4, May 4, 2001
- Section 1, Executive Summary: Replaced references to "campus" with references to all of Emory to be sensitive to the fact that Emory has more than one campus as well as its other relevant locations.
- Did copy editing to improve wording and fix formatting problems.
- Section 3:
- Changed statement that the architecture "provides" a classification scheme to it "envisions" one.
- Removed assumption that the directory service is the only policy store.
- Rewrote paragraph on access to make it widely-supported "interfaces" (plural), to remove presumption of authentication based on the exchange of clear-text passwords, and to remove the mention of "certified" because it imposes too high a barrier to general use of the service.
- Extended the access control paragraph to talk about externalization of authentication.
- Rewrote the access policy data paragraph to make clear that the data you can get depends on the level of trust.
- Section 8.3.3 Standard products Platform Security. Updated File virus scanner to use new name, version & source and drop Norton.
- Section 9: Rewrote part of section 9.2 (Risks configuration) to better explain the current and future states.
- Section 10.1, Issues:
- Added titles to the issues.
- Deleted the first issue about Job Titles, since it was fixed as of April 15, 2001.
- Rewrote old #3 (now #2) to remove assumption that the directory service is the only policy store concerned, and rewrote for clarity.
- Rewrote old #4 (now #3) for clarity in view of the additional implication added to Principle C-7.
- Rewrote old #5 (now #4) to make its intent more clear and to add aspects of reaction to intrusion.
- Section 11, Glossary: Added definition for RFC giving URL to locate them. Added definition of "scan."
- Section 12,
- C-5: Added Implication #2 about proving identity to the authentication service first.
- S-4 & C-6: Balance flexibility and complexity of having a large number of roles.
- C-7:
- Removed "general" from the meaning of "common," since the infrastructure itself may make use of specialized technologies, and the other two words provide enough clarification.
- Added implications to address issues of allowing anyone at Emory who develops an application or service to use the security infrastructure for authentication without imposing a level of security certification or other undue constraints.
- C-9 (Costing and pricing): Added implication including non-monetary cost.
- Leading to version 1.9.3, April 12, 2001
- Page 3-2: Rewrote the paragraph "Classification scheme" to remove the linkage to a particular version of the pending classification policy.
- Page 3-3, Proactive and Reactive Security, changed "breeches" to be "breaches". (What kind of pants are "security breeches" anyway?)
- Section 3.3: Removed suggestion for a diagram to show how domains relate. Having such a diagram is still a good idea.
- Page 5-1, Security Principles, in the second sentence, deleted "subdomains" from "the subdomains assets".
- Section 5.6.1 #1 (Page 5-6): Improved wording for clarification.
- Page 6-1: Updated the descriptions of the Security Analyst and Administrator to better articulate the desired future state and align with the vision on p.3-3.
- Broke up the section "Standard Products--Countermeasures" into subcategories for General Security, Network and Platform to provide a structure parallel to that of the Standards section.
- Sections 7 & 8: Changed code for missing data from "?" to one of NK=Not Known, ND=Not Decided, NC=Not Collected, or NA=Not Applicable, and updated the tables. Added some version numbers and filled in a few other blanks.
- Deleted original Section 8.4, Standard classification scheme, so that the proposed classification guidelines can change without directly affecting the security architecture document.
- Section 11, Glossary:
- Reduced linkage to a particular classification scheme by removing entries that defined confidential, proprietary, public, and restricted using particular classification characteristics.
- Removed redundant "Emory" from entry for ITD.
- Fixed entry for encryption to say it is a process.
- Added an entry for bluetooth, because of its mention as a technology that might have to be supported.
- Made the header repeat at the top of each page.
- Section 12:
- Copy-edited, fixed formatting problems, and improved wording on pages 12-6, 12-11, 12-12, 12-21, 12-23, and 12-29 through 12-32.
- Page 12-17: Moved example here from 12-23 and leaving only a cross-reference to the new location.
- Fixed alignment with security personnel role definitions on pages 12-18, 12-19, 12-33.
- Page 12-23: Removed Implication #5 that mentions the need for a security officer and refers to the appendix, since a security officer is mentioned nowhere else in the document. A Security Analyst probably plays that role.
Leading to Security Architecture v1.9.2, April 9, 2001
- Page 3-2: Rewrote the paragraph "Classification scheme" to reduce the linkage to a particular version of the pending classification policy.
- Section 3.3: Removed suggestion for a diagram to show how domains relate. Having such a diagram is still a good idea.
- Sections 7 & 8: Changed code for missing data from "?" to one of NK=Not Known, ND=Not Decided, NC=Not Collected, or NA=Not Applicable, and updated the tables. Added some version numbers and filled in other blanks.
- Deleted original Section 8.4, Standard classification scheme, so that the proposed classification guidelines can be reviewed independently of the security architecture document.
Leading to Security Architecture v1.9.1, March 27, 2001
- Changed figure numbers to include the section number in conformance with the new template.
- Section 2: Higher quality process diagram & latest template boilerplate.
- Section 3, On page 3-3, Proactive and Reactive Security, "breeches" should be "breaches". (What kind of pants are "security breeches" anyway?)
- On page 5-1, Security Principles, in the second sentence, delete "subdomains" from "the subdomains assets". - Section 5.5: Capitalize "Industry" in CAP C.4.
- Section 7.4: Removed blank in front of "Standards"
- Section 8: Clarified which "architectures" are intended.
- 8.3 Break up Standard Products--Countermeasures into subcategories for General Security, Network and Platform to provide a structure that is parallel to that of the Standards section.
- 8.4 Standard classification scheme: Updated statement about default status of a resource to reflect change in proposed policy.
- Section 11 Glossary: Rewrote definition of scalable to add rapid expansion in scope, availability, reliability and maintainability.
Version 1.9, February 26, 2001
- Initial release for review by the Emory community.