Secure Audit Service Concept Research and Design

Based on the requirements document provided, provide a high level system context diagram and a brief document including the following items:

• List Platform/Tool requirements, assumptions and risks
• Identify major technical risks (things that need to be researched/proven early)
• Identify modules that will need to be designed in detail, and those that may be utilzed as IaaS/PaaS (or identify trade-offs thereof)

We're looking for:

• Options!
• To leverage off-the-shelf services when possible
• To lead in to detailed specifications phase

You are not responsible for detailed design, UML, SDS, etc.  Your goal is to make concrete recommendations for an overall solution.

Here is an excerpt from the full project overview document:

Product stakeholders need to record a history of "important" activities that occur as our software is being utilized in the day to day activities of our customers. For example: the user facing applications in the system may want to record activities like a user changing his password or a new administrator account being created; and the physical device controllers need to record interactions such as a door was unlocked or left ajar for too long.  A reliable historical record of activities considerably reduces risk for stakeholders since it provides evidence of who did what with the system at a given time and place.
 
Stakeholders require a system that will record when and where an identity performs an action on a resource using an application.  Multiple related actions may be correlated.

Final Submission Guidelines

Deliverables

• Provide a diagram that shows the relationship of the proposed infrastructure and softare modules (You may provide multiple diagrams to show optional architectures)
• Provide a single document as desribed in the requirements
• The diagram should be in a commonly viewable image format, preferably: PNG or PDF
• The document should be in a commonly viewable format, preferably PDF, HTML, Markdown, or MS Word Doc