EPIC Opportunity - Cybersecurity - Challenge 2
Main contact
Phoenix, Arizona, United States
Timeline
-
April 15, 2024Experience start
-
April 20, 2024Challenge Week 1
-
April 27, 2024Challenge Week 2
-
May 4, 2024Challenge Week 3
-
May 7, 2024Experience end
Timeline
-
April 15, 2024Experience start
-
April 20, 2024Challenge Week 1
- Meet with client to gain competitor's network design
- Scheduled recurring (or stand-up) meetings with team to discuss progress and assist with removing any obstacles for team members
- Set up team schedule & milestones on Trello and complete risk register (template)
- Create a plan for testing, who owns which parts, how long is needed for each activity?
- Network scan and vulnerability scan using tools. Provide reports from both tools.
- Team reflections are due
-
April 27, 2024Challenge Week 2
- Held recurring (or stand-up) meetings with team to discuss progress and assist with removing any obstacles for team members, understand what is late and why.
- Communicated a summary of progress, and alternative solutions if needed, with stakeholders. Call out any items that are late.
- Exploitation of vulnerability and capture the flag in a text in Desktop of Administrator user either on any of the servers.
- Provide documentation on how the exploit was successful
- Team reflections are due
-
May 4, 2024Challenge Week 3
- Communicated with client submitted remediation report
- Held retrospective meeting with team for phase 2
- Final proposal + report to provide remediation of the vulnerabilities of the server
- Final team reflections are due
-
May 7, 2024Experience end
Experience
1/1 project matches
Dates set by experience
Preferred companies
Phoenix, Arizona, United States
Small to medium enterprise, Social Enterprise, Large enterprise
Any industries
Experience scope
Categories
Security (cybersecurity and IT security) Information technology Networking Project managementSkills
research cybersecurity analysisEPIC aspires to significantly scale high-quality work-based learning experiences through a national network of accredited clearinghouses that provide authentic, employer-led problem-based learning experiences to learners and workers.
This opportunity, provided by the Greater Phoenix Chamber Foundation, offers local businesses to work with learners from Phoenix Coding Academy looking to leverage their development and analysis skills in the arena of cybersecurity to help assess your business' cybersecurity risk.
The learners will collaborate with you on the challenge, how this might be approached, what solutions could be posed and present you with final presentations.
Resources needed:
Access to company staff for interviews and assessment
Access to company infrastructure for assessment
Resources Provided
Support from the Phoenix Coding Academy
Learners
Learners
Workforce Development
Any level
10 learners
Project
90 hours per learner
Educators assign learners to projects
Teams of 5
Employers can expect learners to provide you with an in depth assessment of your business, vulnerabilities and solutions.
Project timeline
-
April 15, 2024Experience start
-
April 20, 2024Challenge Week 1
-
April 27, 2024Challenge Week 2
-
May 4, 2024Challenge Week 3
-
May 7, 2024Experience end
Timeline
-
April 15, 2024Experience start
-
April 20, 2024Challenge Week 1
- Meet with client to gain competitor's network design
- Scheduled recurring (or stand-up) meetings with team to discuss progress and assist with removing any obstacles for team members
- Set up team schedule & milestones on Trello and complete risk register (template)
- Create a plan for testing, who owns which parts, how long is needed for each activity?
- Network scan and vulnerability scan using tools. Provide reports from both tools.
- Team reflections are due
-
April 27, 2024Challenge Week 2
- Held recurring (or stand-up) meetings with team to discuss progress and assist with removing any obstacles for team members, understand what is late and why.
- Communicated a summary of progress, and alternative solutions if needed, with stakeholders. Call out any items that are late.
- Exploitation of vulnerability and capture the flag in a text in Desktop of Administrator user either on any of the servers.
- Provide documentation on how the exploit was successful
- Team reflections are due
-
May 4, 2024Challenge Week 3
- Communicated with client submitted remediation report
- Held retrospective meeting with team for phase 2
- Final proposal + report to provide remediation of the vulnerabilities of the server
- Final team reflections are due
-
May 7, 2024Experience end
Project examples
- Vulnerability Assessment report
- Security Architecture overview and recommendations
- Investigation & Research report
Additional company criteria
Companies must answer the following questions to submit a match request to this experience:
Q1 - Text short
Q2 - Text short
Q3 - Checkbox
Main contact
Phoenix, Arizona, United States
Timeline
-
April 15, 2024Experience start
-
April 20, 2024Challenge Week 1
-
April 27, 2024Challenge Week 2
-
May 4, 2024Challenge Week 3
-
May 7, 2024Experience end
Timeline
-
April 15, 2024Experience start
-
April 20, 2024Challenge Week 1
- Meet with client to gain competitor's network design
- Scheduled recurring (or stand-up) meetings with team to discuss progress and assist with removing any obstacles for team members
- Set up team schedule & milestones on Trello and complete risk register (template)
- Create a plan for testing, who owns which parts, how long is needed for each activity?
- Network scan and vulnerability scan using tools. Provide reports from both tools.
- Team reflections are due
-
April 27, 2024Challenge Week 2
- Held recurring (or stand-up) meetings with team to discuss progress and assist with removing any obstacles for team members, understand what is late and why.
- Communicated a summary of progress, and alternative solutions if needed, with stakeholders. Call out any items that are late.
- Exploitation of vulnerability and capture the flag in a text in Desktop of Administrator user either on any of the servers.
- Provide documentation on how the exploit was successful
- Team reflections are due
-
May 4, 2024Challenge Week 3
- Communicated with client submitted remediation report
- Held retrospective meeting with team for phase 2
- Final proposal + report to provide remediation of the vulnerabilities of the server
- Final team reflections are due
-
May 7, 2024Experience end