Smithsonian / Smithsonian/caas-aspace-scripts
[ARCHER] AU-06 Audit Record Review, Analysis, and Reporting
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 1
Description
Evidence due every 90 days.
Part of the evidence currently provided by Brent.
We also need to provide a snapshot of Splunk logs (for both aspace01 and aspace02). This is currently handled with screenshots embedded in a Word document. Moving forward, we would like to automate a report via Splunk, exported every 90 days, added to our SharePoint directory, with filenames such as "AU-06_{date}".
Evidence due next prior to 2025-0608.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named; first clarify how Splunk exports and the SharePoint directory are accessed, and where this repository should automate the process. Done means producing a Splunk log snapshot for aspace01 and aspace02 every 90 days, with filenames such as AU-06_{date}, and placing the report in SharePoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100