This community app provides distributed cyber practitioners with access to knowledge beyond their immediate circle. 

## Empowering cyber-practitioners

Individual practitioners find it difficult to keep up with cyber threats' rapid and at-scale expansion.

In large organisations where divisions or subsidiaries employ their own cybersecurity professionals or staff have cyber within their broader job responsibilities, there is a need to foster a voluntary community of practice where knowledge is shared. 

This is also true in healthcare, education, and local government.

This is where the Cyber Community app comes into its own.  

## Why an app?

There's no digital divide for those familiar with apps, with features like threat updates and threat defence strategies at their fingertips. Users can access a checklist for cyber hygiene, know how to reach out instantly regardless of time or location and find links to educational resources and community details within the app. 

The app aims to foster a cyber community, educate specialists and non-specialists, streamline incident management, boost awareness, decrease vulnerabilities, minimise harm, enhance recovery and resilience, empower providers with suppliers, mitigate attack impact through insurance, and increase organisational control posture.

## Developer notes 1

1. The statements of 'will' and 'can' above assume that the application developer using the template will populate tables and provide links specific to their requirements.  The app is not an off-the-shelf Cyber handbook - that is not possible or practical. 

2. The Glide version of the app is built on simple tables using standard functionality.  The UI is crisp, keeping it uncluttered for accessibility.  Users come from varied backgrounds and tend to use only one or two screens to execute their responsibilities, so I have avoided over-engineering the design.

3. I have not put column or row restrictions in the app.  My design is based on this being used for non-privileged information - meaning the only information stored in the app is publicly available. Users are not required to provide proof of identity and are advised to use pseudonyms in their profiles.

4. [The one point of security would be to limit the type of detail a user puts into their incident log (Emergency form).]

## Developer notes 2

1. Glide developers will easily replace the manual table updates with integration with Google Docs.
2. The contact buttons (phone, email, WhatsApp) are not configured.
3. The chat function is not configured.

Working screens / functions cover the essentials of cyber awareness, defence and response.
-- Incident History
-- Current threats
-- Emergency registration of an incident
-- Schedule of events
-- Provider list - service provider to the community
-- Supplier list - suppliers of services to the app users, including cybersecurity agencies
-- Link to Learning resources
-- Gamification to engage users
--- Screen for tracking metrics (such as compliance scores)
--- Screen for tracking results of weekly cyber pop-quiz (quiz function excluded)


##Future notes

I will ultimately want to build in an AI chat function so that the cyber professional can get real time defend and respond advice across many platforms.  The type of organisation I have designed this for has many autonomous bodies and a variety of technologies in place, therefore no set FAQ can respond to every user need.

>> I am putting a nominal price on the template to support my habit of good coffee and late nights developing.

Templates by Jeremy Farrell