Concept skos:Concept Code PR.PS-05.1

Web and e-mail filters shall be installed and used.

Also known as

skos:altLabel

Web and email filtering

Note

skos:note

The goal of this control is to reduce the risk of malware infections, phishing attacks, and data breaches by implementing and maintaining effective web and email filtering solutions. To support this goal, the organisation should:

  • Implement Web Filtering Web filters should be used to control access to websites based on:
    • Predefined allow/block lists (e.g. by URL or domain)
    • Real-time content analysis to detect malicious or inappropriate content
    • Techniques such as URL filtering, content filtering, DNS filtering, and client- or server-side filtering
  • Configure Email Filtering Email filters should be configured to:
    • Block spam, phishing attempts, and malicious attachments or links
    • Categorise incoming emails (e.g. newsletters, social media alerts) to reduce clutter and improve awareness
    • Scan for known threats and suspicious patterns to enhance email security
  • Keep Filters Updated Filtering rules and threat databases should be updated regularly to respond to evolving threats.
  • Integrate with Security Policies Web and email filtering should align with the broader organisational security policies and awareness efforts.
  • Include OT Considerations In OT environments, internet and email access should be restricted to only what is operationally necessary. Filtering should be applied to any systems with external connectivity to prevent exposure to threats.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_PR_PS_05_1
All data (23 statements)

Properties and relations

Direct links from the subject.

Property Value

type

The subject is an instance of a class.

http://cyfun.data.gift/ontology#Requirement

type

The subject is an instance of a class.

Concept

An idea or notion; a unit of thought.

label

A human-readable name for the subject.

PR.PS-05.1: Web and e-mail filters shall be installed and used.

http://cyfun.data.gift/ontology#requirementId

PR.PS-05.1

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p36

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p87

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p126

has broader

Relates a concept to a concept that is more general in meaning.

http://cyfun.data.gift/data/subcategory_PR.PS-05

note

A general note, for any purpose.

The goal of this control is to reduce the risk of malware infections, phishing attacks, and data breaches by implementing and maintaining effective web and email filtering solutions. To support this goal, the organisation should: - Implement Web Filtering Web filters should be used to control access to websites based on: - Predefined allow/block lists (e.g. by URL or domain) - Real-time content analysis to detect malicious or inappropriate content - Techniques such as URL filtering, content filtering, DNS filtering, and client- or server-side filtering - Configure Email Filtering Email filters should be configured to: - Block spam, phishing attempts, and malicious attachments or links - Categorise incoming emails (e.g. newsletters, social media alerts) to reduce clutter and improve awareness - Scan for known threats and suspicious patterns to enhance email security - Keep Filters Updated Filtering rules and threat databases should be updated regularly to respond to evolving threats. - Integrate with Security Policies Web and email filtering should align with the broader organisational security policies and awareness efforts. - Include OT Considerations In OT environments, internet and email access should be restricted to only what is operationally necessary. Filtering should be applied to any systems with external connectivity to prevent exposure to threats.

note

A general note, for any purpose.

The goal of this control is to reduce the risk of malware infections, phishing attacks, and data breaches by implementing and maintaining effective web and email filtering solutions. To support this goal, the organisation should: - Implement Web Filtering Web filters should be used to control access to websites based on: - Predefined allow/block lists (e.g. by URL or domain) - Real-time content analysis to detect malicious or inappropriate content - Techniques such as URL filtering, content filtering, DNS filtering, and client- or server-side filtering - Configure Email Filtering Email filters should be configured to: - Block spam, phishing attempts, and malicious attachments or links - Categorise incoming emails (e.g. newsletters, social media alerts) to reduce clutter and improve awareness - Scan for known threats and suspicious patterns to enhance email security - Keep Filters Updated Filtering rules and threat databases should be updated regularly to respond to evolving threats. - Integrate with Security Policies Web and email filtering should align with the broader organisational security policies and awareness efforts. - Include OT Considerations In OT environments, internet and email access should be restricted to only what is operationally necessary. Filtering should be applied to any systems with external connectivity to prevent exposure to threats.

note

A general note, for any purpose.

The goal of this control is to reduce the risk of malware infections, phishing attacks, and data breaches by implementing and maintaining effective web and email filtering solutions. To support this goal, the organisation should: • Implement Web Filtering Web filters should be used to control access to websites based on: o Predefined allow/block lists (e.g. by URL or domain) o Real-time content analysis to detect malicious or inappropriate content o Techniques such as URL filtering, content filtering, DNS filtering, and client- or server-side filtering • Configure Email Filtering Email filters should be configured to: o Block spam, phishing attempts, and malicious attachments or links o Categorise incoming emails (e.g. newsletters, social media alerts) to reduce clutter and improve awareness o Scan for known threats and suspicious patterns to enhance email security • Keep Filters Updated Filtering rules and threat databases should be updated regularly to respond to evolving threats. • Integrate with Security Policies Web and email filtering should align with the broader organisational security policies and awareness efforts. • Include OT Considerations In OT environments, internet and email access should be restricted to only what is operationally necessary. Filtering should be applied to any systems with external connectivity to prevent exposure to threats.

note

A general note, for any purpose.

<div><p>The goal of this control is to reduce the risk of malware infections, phishing attacks, and data breaches by implementing and maintaining effective web and email filtering solutions. To support this goal, the organisation should:</p><ul><li>Implement Web Filtering Web filters should be used to control access to websites based on:<ul><li>Predefined allow/block lists (e.g. by URL or domain)</li><li>Real-time content analysis to detect malicious or inappropriate content</li><li>Techniques such as URL filtering, content filtering, DNS filtering, and client- or server-side filtering</li></ul></li><li>Configure Email Filtering Email filters should be configured to:<ul><li>Block spam, phishing attempts, and malicious attachments or links</li><li>Categorise incoming emails (e.g. newsletters, social media alerts) to reduce clutter and improve awareness</li><li>Scan for known threats and suspicious patterns to enhance email security</li></ul></li><li>Keep Filters Updated Filtering rules and threat databases should be updated regularly to respond to evolving threats.</li><li>Integrate with Security Policies Web and email filtering should align with the broader organisational security policies and awareness efforts.</li><li>Include OT Considerations In OT environments, internet and email access should be restricted to only what is operationally necessary. Filtering should be applied to any systems with external connectivity to prevent exposure to threats.</li></ul></div>

notation

A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme.

PR.PS-05.1

alternative label

skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.

Web and email filtering

preferred label

A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag.

Web and e-mail filters shall be installed and used.

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_delta_BASIC

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_BASIC

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_IMPORTANT

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_ESSENTIAL

http://cyfun.data.gift/ontology#level

http://cyfun.data.gift/data/level_BASIC

triple count

The number of triples associated with the subject.

21

in dataset

Specifies the dataset the subject is part of.

http://data.gift/d/datasets/69E8863AA6CE46D9ACD13109

Resultaten 1 - 23 of 23

References

Inverse links to the subject.