711649924b
* Some initial refactoring * Make it one application * Got it working * Fix problem on Windows * Move WebWolf * Move first lesson * Moved all lessons * Fix pom.xml * Fix tests * Add option to initialize a lesson This way we can create content for each user inside a lesson. The initialize method will be called when a new user is created or when a lesson reset happens * Clean up pom.xml files * Remove fetching labels based on language. We only support English at the moment, all the lesson explanations are written in English which makes it very difficult to translate. If we only had labels it would make sense to support multiple languages * Fix SonarLint issues * And move it all to the main project * Fix for documentation paths * Fix pom warnings * Remove PMD as it does not work * Update release notes about refactoring Update release notes about refactoring Update release notes about refactoring * Fix lesson template * Update release notes * Keep it in the same repo in Dockerhub * Update documentation to show how the connection is obtained. Resolves: #1180 * Rename all integration tests * Remove command from Dockerfile * Simplify GitHub actions Currently, we use a separate actions for pull-requests and branch build. This is now consolidated in one action. The PR action triggers always, it now only trigger when the PR is opened and not in draft. Running all platforms on a branch build is a bit too much, it is better to only run all platforms when someone opens a PR. * Remove duplicate entry from release notes * Add explicit registry for base image * Lesson scanner not working when fat jar When running the fat jar we have to take into account we are reading from the jar file and not the filesystem. In this case you cannot use `getFile` for example. * added info in README and fixed release docker * changed base image and added ignore file Co-authored-by: Zubcevic.com <rene@zubcevic.com>
26 lines
1.3 KiB
Plaintext
26 lines
1.3 KiB
Plaintext
== Confidentiality
|
|
|
|
Confidentiality is "the property that information is not made available or disclosed to unauthorized individuals, entities, or processes." In other words, confidentiality requires that unauthorized users should not be able to access sensitive resources. Confidentiality must be balanced with availability; authorized persons must still access the resources they have been granted permissions for.
|
|
|
|
Although confidentiality is similar to "privacy," these two words are not interchangeable. Instead, confidentiality is a component of privacy; confidentiality is implemented to protect resources from unauthorized entities.
|
|
|
|
{nbsp} +
|
|
|
|
=== Examples that compromise confidentiality:
|
|
|
|
** a hacker gets access to the password database of a company
|
|
** a sensitive email is sent to the incorrect individual
|
|
** a hacker reads sensitive information by intercepting and eavesdropping on an information transfer
|
|
|
|
{nbsp} +
|
|
|
|
=== Examples of methods ensuring confidentiality
|
|
|
|
** data encryption
|
|
** properly implemented authentication and access control
|
|
*** securely stored passwords
|
|
*** multi-factor authentication (MFA)
|
|
*** biometric verification
|
|
** minimizing the number of places/times the information appears
|
|
** physical security controls such as properly secured server rooms
|