Skip to content

Update README for recent updates #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
edthedev merged 2 commits into from
Oct 1, 2026
Merged

Update README for recent updates #14

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3c754b8
Update README for recent updates
edthedev Sep 29, 2026
a5f9c2f
Add link to Code Risk Discussion guide
edthedev Sep 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,12 +20,13 @@ for information about our development standards.

### Cybersecurity Review

- SecDev maintains an AI "skill", `/cybersecurity-review` for identifying vulnerabilities in local source code.
- We update this AI skill after OWASP updates the OWASP Top Ten, roughly every four years.
- This skill is intended to guide remediation efforts and is not a substitute for a mature Software Development Lifecycle.
- The Cybersecurity Development team at the University of Illinois maintains these AI "skills", `/code-risk` and `/code-cost` for identifying possible vulnerabilities and maintenance costs in local source code.
- We update this AI "skill" after OWASP updates the OWASP Top Ten, roughly every four years.
- This "skill" is intended to guide remediation efforts and is not a substitute for a mature Software Development Lifecycle.
- We consider this skill suitable for exploration and education.
- We want to help interpret and respond to these reports - they can be confusing, may contain false positives, and will raise questions.
- Campus IT Professionals can contact securitysupport@illinois.edu.
- We recommend also requesting a [Code Risk Discussion](https://answers.uillinois.edu/illinois/106153) engagement for more sensitive code, as we find that Code Risk Discussions catch issues that these "skills" cannot.
- Campus faculty and staff responsible for custom code supporting campus users can contact securitysupport@illinois.edu for assistance.

## Installation

Expand Down
Loading