COMP 6660 · Online Participation Discussion Forums

COMP 6660 · Assessment · Online Participation

COMP 6660 · Enterprise Cybersecurity Online Participation

The online participation component is intended to foster scholarly discussion, professional knowledge sharing, critical reflection, and collaborative learning in enterprise cybersecurity. It is assessed through six structured discussion forums aligned with the six course units.

Read the brief Course home
Weight: 10% of final grade Coverage: All six units Format: Asynchronous discussion forums

01 Overview

The online participation component accounts for 10% of the final course grade. It is assessed through six structured discussion forums — one aligned with each of the six course units — in which students engage critically with the course material, with the scholarly and industry literature, and with each other.

Participation is not a formality. Enterprise cybersecurity is fundamentally a professional practice conducted through discussion, debate, and the exchange of informed views. The online participation component develops the capabilities that professional practice requires — the ability to read critically, to reason clearly, to communicate persuasively, to engage constructively with opposing views, and to learn from peers. These capabilities are developed through sustained engagement, not through a single contribution.

Participation takes place asynchronously through discussion forums integrated within the Brightspace learning environment. There is no requirement for synchronous attendance. However, the forums are threaded discussions — contributions build on each other — so periodic, timely engagement is more valuable than a single end-of-unit contribution.

Purpose

  • To develop scholarly discussion skills — critical engagement, evidence-based argumentation, and constructive debate.
  • To develop professional communication skills — the ability to write clearly and persuasively for a technical and managerial audience.
  • To promote peer learning — the exchange of experience, perspectives, and insight among students from diverse professional backgrounds.
  • To connect theory to practice — by applying course concepts to the enterprises and sectors in which students work.
  • To develop the habits of reflection and critical thinking that professional practice requires.

Structure

  • Six forums — one aligned with each course unit.
  • Initial contribution — one substantive posting of 300–500 words per forum.
  • Peer responses — at least two meaningful responses per forum.
  • Cadence — each forum remains open for the duration of its unit, with the contribution expected within the unit window.
  • Moderation — facilitated by the instructor and, where appropriate, by teaching assistants.

Weight and value

  • Weight: 10% of the final course grade.
  • Contribution to CLOs: CLO1, CLO2, CLO9.
  • Assessment: Per-forum rubric, aggregated across the six forums.
  • Estimated effort: 1–2 hours per week across the term, plus preparation time.

Why participation matters

  • The discussion forums are where the course material becomes your own — through explanation, application, and debate.
  • The forums are where you benefit from your peers' experience — and where you contribute your own.
  • The forums are where the professional skills of scholarly communication are developed — skills that no other component of the course exercises to the same degree.

How to approach participation

Begin each unit by engaging with the discussion forum prompt and with the lesson material. Read widely — the forum prompts invite you to engage with scholarly and industry literature, and the quality of your contribution reflects the quality of your reading. Write your initial contribution deliberately — plan what you will argue, support it with evidence, and connect it to the course material and to your own professional context. Then engage with your peers — not with simple agreement, but with thoughtful responses that extend, question, or challenge the ideas presented. The strongest discussions are those in which participants build on each other's contributions, disagree productively, and reach insights that no single contributor reached alone.

02 Learning outcomes assessed

The online participation component contributes primarily to the following Course Learning Outcomes (CLOs):

Course learning outcomes supported by online participation
CLO Description How participation contributes
CLO1 Define the scope, objectives, principles, and strategic importance of enterprise cybersecurity. Forum 1 and Forum 6 — engagement with the foundational concepts and the strategic dimensions of enterprise cybersecurity.
CLO2 Analyse cybersecurity threats, vulnerabilities, risks, and attack vectors affecting enterprise environments. Forum 3 and Forum 5 — analysis of threats, risks, and the vulnerabilities in enterprise systems and infrastructure.
CLO9 Conduct scholarly research and communicate cybersecurity findings effectively. All forums — the ability to read and synthesise sources, to develop reasoned arguments, and to communicate them effectively in written discussion.

The forums also provide indirect support for other CLOs — particularly CLO3–CLO8 — by engaging students with the material across the whole course and by developing the analytical and communication capabilities those CLOs require.

03 Logistics and schedule

Participation logistics
Item Detail
Platform Discussion forums in Brightspace — accessible from the Course home and from the Unit pages.
Access Each forum opens at the start of the unit to which it is aligned and remains open throughout the course.
Expected cadence Contribution to each forum is expected within the unit window. Late contributions are accepted but may attract a reduced mark, as they do not contribute to the discussion during its active phase.
Word count Initial contribution: 300–500 words. Peer responses: 100–250 words each.
Minimum requirements One initial contribution and at least two peer responses per forum.
Moderation Facilitated by the instructor and teaching assistants. The instructor may prompt, redirect, or summarise discussion where appropriate.
Marking Marked per forum using the participation rubric (see Section 07). Marks are aggregated across the six forums to produce the participation component mark.
Feedback Aggregate feedback is provided after each unit. Individual contributions are not commented on line by line — but the instructor may provide guidance where a pattern across contributions requires it.

Schedule alignment

Forum schedule alignment
Forum Unit Weeks open Contribution expected by
Forum 1 Unit 1 — Foundations Weeks 1–2 End of Week 2
Forum 2 Unit 2 — Core Technologies and Access Control Weeks 3–5 End of Week 5
Forum 3 Unit 3 — Threats, Risks, Vulnerabilities, and Attacks Weeks 6–7 End of Week 7
Forum 4 Unit 4 — Security Architectures and Technologies Weeks 8–9 End of Week 9
Forum 5 Unit 5 — Systems and Infrastructure Security Weeks 10–11 End of Week 11
Forum 6 Unit 6 — Governance, Risk, and Compliance Weeks 12–13 End of Week 13

Timing of contributions

Contribution early in the unit is more valuable than contribution late — because an early contribution shapes the discussion that follows, and because a late contribution does not benefit from the responses that precede it. Aim to contribute your initial posting within the first half of each unit window, and to respond to your peers over the days that follow.

04 The six forums

Each forum is aligned with one of the six course units and focuses on the themes that the unit examines. The example discussion topics below indicate the kind of questions the forums explore — the instructor may refine or reframe them within each unit, and may respond to current developments with additional prompts.

Forum 1 — Foundations of Enterprise Cybersecurity

Aligned with: Unit 1 · Open: Weeks 1–2

This forum engages with the foundations of enterprise cybersecurity — the strategic importance of the field, the threat landscape, and the challenges that enterprises face in managing their security.

Example discussion topics

  • Lessons learned from major cyber incidents. Analyse a major cyber incident — a breach, a disruptive attack, a destructive incident — and identify what it reveals about the state of enterprise cybersecurity practice. What did the enterprise get wrong? What did it get right? What should other enterprises learn from the incident?
  • Emerging cybersecurity threats. Identify a threat that is currently emerging — a new technique, a new adversary group, a new attack vector — and analyse its implications for enterprise security. What makes this threat significant? How should enterprises respond?
  • Enterprise security challenges. Identify a challenge that enterprises face in managing their security — organisational, technical, cultural, or regulatory — and analyse it. What makes the challenge difficult? What would it take to address it?

Forum 2 — Identity, Access Control, and Zero Trust

Aligned with: Unit 2 · Open: Weeks 3–5

This forum engages with cryptography, identity, access control, and Zero Trust — the core technologies through which enterprise systems are protected.

Example discussion topics

  • Zero Trust adoption experiences. Share your experience with Zero Trust — either as a practitioner or as an observer — and analyse what makes Zero Trust adoption difficult. What worked? What did not? What advice would you offer an enterprise considering Zero Trust?
  • MFA effectiveness. Analyse the effectiveness of multi-factor authentication — its security properties, its limitations, its usability, and its adoption challenges. What does the evidence suggest about which MFA methods are most effective? What remains contested?
  • IAM challenges. Identify a challenge in Identity and Access Management — technical, organisational, or operational — and analyse it. What makes IAM difficult in practice? What approaches have you seen succeed?

Forum 3 — Threat Intelligence and Risk Management

Aligned with: Unit 3 · Open: Weeks 6–7

This forum engages with the threat landscape, threat modelling, vulnerability assessment, risk management, and the adversary ecosystem.

Example discussion topics

  • Risk assessment methodologies. Compare two or more risk assessment methodologies — qualitative, semi-quantitative, or quantitative approaches — and analyse their relative strengths and limitations. Which methodology is most appropriate for which organisational context?
  • Ransomware trends. Analyse the current state of ransomware — its evolution, its business model, its impact, and the defensive strategies that are most effective. What is the evidence about what works?
  • Supply-chain attacks. Analyse a supply-chain attack — a documented incident or a hypothetical scenario — and examine the specific challenges that supply-chain attacks present for detection, for response, and for vendor management.

Forum 4 — Enterprise Security Architectures

Aligned with: Unit 4 · Open: Weeks 8–9

This forum engages with security architecture principles, defence in depth, network security, and the technologies — IDS, IPS, SIEM, XDR — through which enterprise systems are monitored and defended.

Example discussion topics

  • Security architecture patterns. Analyse a security architecture pattern — zero trust, defence in depth, micro-segmentation, or another pattern — and evaluate its effectiveness, its applicability, and its limitations. What does the pattern achieve? What does it not?
  • SOC implementation. Analyse what makes a Security Operations Centre effective — the people, the technology, the processes, and the culture. What are the common failure modes? What distinguishes the SOCs that work from those that do not?
  • Cloud security architectures. Analyse a cloud security architecture — the shared responsibility model, the identity architecture, the network design — and evaluate the specific security considerations that cloud environments introduce.

Forum 5 — Systems and Infrastructure Security

Aligned with: Unit 5 · Open: Weeks 10–11

This forum engages with the security of operating systems, endpoints, applications, databases, cloud environments, containers, mobile devices, IoT, and critical infrastructure.

Example discussion topics

  • Cloud security governance. Analyse the governance challenges that cloud environments introduce — the shared responsibility model, the configuration complexity, the identity sprawl, the provider dependency — and examine how enterprises should address them.
  • Container security. Analyse the specific security considerations of container environments — the shared kernel, the image supply chain, the orchestration control plane, the runtime — and evaluate the controls that are most effective.
  • Critical infrastructure protection. Analyse the specific security challenges of operational technology and critical infrastructure — the safety considerations, the legacy estates, the operational constraints — and evaluate the approaches that are appropriate in those environments.

Forum 6 — Cybersecurity Governance and Resilience

Aligned with: Unit 6 · Open: Weeks 12–13

This forum engages with governance, risk management, compliance, incident response, business continuity, cyber resilience, and the emerging trends that are reshaping enterprise cybersecurity.

Example discussion topics

  • NIST CSF versus ISO 27001. Compare NIST CSF 2.0 and ISO/IEC 27001 — their scope, their structure, their governance requirements, their certification models — and analyse how enterprises should choose between them, or integrate them.
  • Incident response practices. Analyse what makes incident response effective — the preparation, the detection, the containment, the communication — and evaluate the common failure modes. What distinguishes the organisations that respond well?
  • AI and cybersecurity governance. Analyse the governance challenges that artificial intelligence introduces for enterprise cybersecurity — the security of AI systems, the use of AI by adversaries, the governance of AI decisions, the regulatory obligations — and evaluate how enterprises should respond.

Engaging with the forum prompts

The forum prompts are starting points — not constraints. You may engage with any of the topics listed for each forum, propose a related topic of your own, or respond to a topic raised by a peer. The strongest discussions frequently emerge when participants bring their own experience and perspective to the material — a specific incident from your sector, a challenge you have encountered in practice, or a development you have been following. Where your experience provides evidence or insight that the published literature does not, share it — subject, of course, to professional confidentiality and to the sensitivity of the material.

05 Participation requirements

For each forum, students are expected to make one substantive initial contribution and at least two meaningful peer responses.

Initial contribution

One substantive posting of approximately 300–500 words that:

  • Demonstrates understanding of the readings. Your contribution should demonstrate that you have engaged with the relevant lesson material and with the scholarly and industry sources the topic requires. It should be clear that you have read, not merely skimmed.
  • Incorporates scholarly sources. Your contribution should cite at least two or three sources — peer-reviewed papers, standards, or authoritative industry publications. Cite them properly (APA 7th, IEEE, or Harvard — consistently).
  • Contributes original analysis. Your contribution should not merely summarise — it should analyse. Offer an interpretation, a critique, a comparison, or an argument. Say something that is yours.
  • Links theory to practice. Where possible, connect the material to your own professional context, to a documented case, or to a realistic enterprise scenario. The forums are a place for abstract concepts to meet concrete situations.
  • Engages with the topic. Address the forum topic directly — do not simply write about enterprise cybersecurity in general terms.
  • Is professionally written. Clear, well-organised, and free of grammatical and spelling errors. This is professional communication, not informal chat.

Peer responses

At least two meaningful responses to classmates per forum. Each response should be approximately 100–250 words. Responses should:

  • Extend the discussion. Add something to what has been said — a further example, an alternative perspective, a specific consequence, an additional source.
  • Critically evaluate ideas. Engage with the substance of what your peer has written — not with their writing style, their grammar, or their use of terminology.
  • Present alternative perspectives. Where you disagree with your peer — or where you think their analysis is incomplete — say so, respectfully and with reasons. Productive disagreement is a feature of scholarly discussion, not a fault.
  • Introduce supporting evidence or examples. Where your response makes a claim, support it — with a source, an example, or a reasoned argument.
  • Be professional and constructive. Respond to the contribution, not to the contributor. Critique ideas, not people. Where you disagree, explain why — and acknowledge what the peer's contribution does well.

Simple agreement statements — "I agree," "Great point," "Thanks for sharing" — are not sufficient as peer responses. They do not contribute to the discussion and they will not be counted toward the participation requirement.

Minimum and maximum

  • Minimum. One initial contribution and two peer responses per forum. Contributions below the minimum will be reflected in the participation mark for that forum.
  • Maximum. There is no formal maximum, but quality matters more than quantity. A small number of substantive, well-argued contributions is worth more than a large number of superficial posts.
  • Distribution. Contributions should be distributed across the unit window — not concentrated at the end. Early contributions shape the discussion; late contributions miss it.

What does not count

  • Off-topic posts. Posts that do not engage with the forum topic or that are unrelated to enterprise cybersecurity.
  • Simple agreement. Responses that only agree with another student without adding anything.
  • Summaries without analysis. Posts that summarise the readings without offering any interpretation, critique, or original insight.
  • Unsourced claims. Posts that make significant claims without reference to sources or evidence.
  • Unprofessional posts. Posts that are disrespectful, aggressive, or that do not meet the standards of professional communication.

The most common participation failure

The most common participation failure is treating the forums as an obligation to be discharged rather than as an opportunity to learn. Contributions that summarise the readings without offering analysis, that agree with peers without adding to the discussion, or that are written hastily without engaging with the sources — these meet the minimum requirement but do not develop the capabilities the participation component is designed to develop. The strongest participation comes from students who read widely, think carefully, and write deliberately — and who engage with the discussion as they would engage with a professional conversation.

06 Scholarly discussion guidance

The forums are scholarly discussions, not informal chat. The distinction matters — scholarly discussion has standards, and those standards are what the participation component assesses.

What distinguishes scholarly discussion

  • It is evidence-based. Claims are supported by evidence — from the course material, from published sources, from documented cases, or from professional experience. Where evidence is absent, the discussion notes the gap.
  • It is critical. Sources are not accepted uncritically — their assumptions, their methods, and their limitations are examined. Arguments are evaluated, not merely reported.
  • It is reasoned. Conclusions follow from premises, and the reasoning is made explicit. Where there is uncertainty, the uncertainty is acknowledged.
  • It is constructive. Contributions build on what others have said — extending, questioning, or refining. The objective is to advance understanding, not to win an argument.
  • It is professionally communicated. Clear, well- organised, and respectful. Disagreement is expressed with reasons and without personal animosity.
  • It is context-aware. Contributions acknowledge the context — the sector, the organisation, the regulatory environment — in which the analysis applies. Generalisations are qualified where appropriate.

Reading for discussion

  • Read widely. The forum prompts invite engagement with scholarly and industry literature. Read beyond the lesson material — at least one or two sources beyond what the lesson references.
  • Read critically. As you read, ask: what is the author's argument? What is the evidence? What are the assumptions? Where are the limitations? How does this relate to what I already know?
  • Take notes. Note the key claims, the supporting evidence, the sources, and your own reactions. This will make writing your contribution much easier.
  • Identify the contested questions. Where sources disagree — and they frequently do — the disagreement is a productive starting point for discussion. Engage with the disagreement rather than smoothing it over.
  • Connect to your experience. Your professional experience is a source of evidence that is frequently not available in the published literature. Where your experience is relevant, draw on it.

Writing for discussion

  • Plan your contribution. Before writing, decide what you will argue. What is your central claim? What evidence supports it? What will you say that others might not?
  • Structure your contribution. A well-organised 300–500-word contribution has a clear structure — an opening claim, supporting analysis, and a conclusion or an invitation to further discussion.
  • Be specific. General statements about the importance of security are not analysis. Be specific about what you claim, why you claim it, and what the implications are.
  • Support claims with evidence. Where you make a claim, support it — with a source, a case, or a reasoned argument. Cite your sources properly.
  • Acknowledge uncertainty. Where the evidence is unclear, or where your conclusion depends on assumptions, say so. Intellectual humility is a strength, not a weakness.
  • Be concise. The word count is a guide — say what you need to say well, and stop. A well-written 350-word contribution is more effective than a rambling 700-word one.
  • Proofread. Read your contribution before posting. Check for grammar, spelling, and clarity. Contributions that are difficult to read are difficult to respond to.

Responding to peers

  • Read carefully. Read your peer's contribution fully before responding. Respond to what they actually said, not to what you assumed they would say.
  • Engage with the substance. Identify the specific claims your response addresses. Quote where helpful.
  • Add something. Your response should extend the discussion — with a further example, an alternative perspective, a specific consequence, or an additional source.
  • Disagree respectfully. Where you disagree, say so — and explain why. Disagreement is a feature of scholarly discussion, not a fault. But it must be reasoned, not personal.
  • Acknowledge strengths. Where your peer's contribution is strong — a well-made argument, a useful source, an interesting example — acknowledge it. Recognition is part of constructive discussion.
  • Keep it concise. Responses should be 100–250 words. Focus on the substance; do not pad.

The test of a strong contribution

A useful test for any contribution is: does this add something that would not have been there without me? If your contribution merely repeats what the lesson material or another student has already said, it has not added value. If it offers an interpretation, an example, a critique, a comparison, a question, or a connection that was not previously in the discussion — it has. Aim to contribute something that is yours.

07 Participation rubric

Each forum is marked against the following rubric. The marks for the six forums are aggregated to produce the participation component mark.

Participation rubric
Criterion Weight What the marker looks for
Relevance and Quality of Contributions 30% Contributions engage directly with the forum topic. They are substantive, well-organised, and clearly written. They demonstrate understanding of the relevant material and address the question at hand rather than drifting to adjacent topics.
Critical Analysis and Reflection 30% Contributions analyse rather than summarise. They offer interpretation, critique, comparison, or argument. They recognise complexity, acknowledge trade-offs, and engage with contested questions. They connect the material to professional practice or to realistic enterprise contexts.
Integration of Research Evidence 20% Contributions incorporate scholarly and authoritative sources — at least two or three per initial contribution. Sources are relevant, correctly cited, and integrated into the argument rather than listed. Claims are supported by evidence.
Engagement with Peers 20% Peer responses are meaningful — they extend the discussion, critically evaluate ideas, present alternative perspectives, or introduce supporting evidence or examples. Simple agreement statements do not meet the requirement. Responses are timely, constructive, and professional.

Grade descriptors for participation

Participation grade descriptors
Grade Range Description
A (Excellent) 85–100% Contributions are consistently substantive, well-argued, and professionally communicated. They demonstrate deep engagement with the sources and with the discussion. Peer responses are meaningful, constructive, and add to the discussion. Original insight is evident across the forums.
B (Good) 70–84% Contributions are relevant, well-organised, and demonstrate solid understanding. They incorporate appropriate sources and offer some analysis. Peer responses are meaningful. Some contributions may lack the depth, originality, or nuance of an A-grade submission.
C (Satisfactory) 60–69% Contributions meet the minimum requirements in content and length. They demonstrate adequate understanding and incorporate sources. Peer responses engage with others. However, contributions may be largely descriptive rather than analytical, or may lack original insight.
D (Marginal) 50–59% Contributions are below the minimum in some forums, or are superficial, or do not adequately engage with the topic. Peer responses may be simple agreement statements. Sources may be absent or inadequately integrated.
F (Unsatisfactory) 0–49% Contributions are absent, substantially below the minimum, off-topic, or unprofessional. Peer responses are absent or do not meet the requirement.

Aggregation across forums

  • Each forum is marked out of 100 against the rubric.
  • The participation component mark is the average of the six forum marks, weighted equally.
  • Where a student has not contributed to a forum, that forum receives a mark of zero — which significantly affects the aggregate.
  • Where a student contributes substantially more than the minimum, the marker may consider the additional contribution — but the primary assessment is based on the required contribution and responses.

Feedback on participation

  • Aggregate feedback. After each forum, the instructor provides aggregate feedback — highlighting what the cohort did well and identifying where contributions could be strengthened.
  • Individual marks. Individual forum marks are posted in Brightspace. Marks are not provided as line-by-line commentary.
  • Pattern-based guidance. Where an individual's contributions show a consistent pattern — for example, consistently descriptive rather than analytical — the instructor may provide specific guidance.
  • Mid-term feedback. A summary of participation performance is provided after Forum 3, so that students can adjust their approach if required.

08 Examples of strong and weak contributions

The examples below are illustrative — they show the kind of contribution that attracts high and low marks, and they identify what distinguishes them.

Weak initial contribution

Ransomware is a major threat to enterprises. Many organisations have been affected by ransomware and it costs them a lot of money. It is important to have good backups and to train employees not to click on phishing emails. Enterprises should implement defence in depth and use the NIST framework. In conclusion, ransomware is a serious problem that enterprises need to take seriously.

What is wrong with it?

  • It is generic — it could have been written about any topic.
  • It is a list of assertions without evidence or sources.
  • It does not engage with the forum prompt.
  • It contains no analysis — no interpretation, critique, or comparison.
  • It does not connect to anything specific — not a source, not a case, not a professional context.

Strong initial contribution

One of the most significant shifts in the ransomware landscape over the past three years has been the emergence of data-theft extortion alongside encryption — what industry reporting calls "double extortion." The shift has a specific consequence that is frequently overlooked: organisations that have invested heavily in backup and recovery — the control that was previously the most effective defence against ransomware — discover that recovery does not address the extortion threat. Once the data has been exfiltrated, the adversary has leverage that recovery cannot eliminate.

This is what makes the modern ransomware threat qualitatively different from its predecessor. A 2021 study by [author] examined the shift and argued that [specific finding]. The evidence is consistent with the pattern observed in [specific incident], where the enterprise's tested backup capability did not reduce the pressure to pay — because the data had already been exfiltrated.

The implication for enterprise defence is significant. Prevention and recovery remain necessary, but neither addresses the extortion threat directly. What does address it — or reduce it — is contested. Some practitioners argue that a firm no-payment policy, publicly stated and consistently applied, reduces the enterprise's attractiveness as a target. Others argue that the evidence for this is weak, and that the decision is ultimately contextual — shaped by the data involved, the regulatory environment, and the enterprise's financial position. I would argue that the debate misses a more fundamental point: the effective response to double extortion is to reduce the value of the data to the adversary — through classification, through minimisation, through the elimination of data that does not need to be retained. This is not a control most enterprises currently operate, and it represents a significant gap in the standard defence framework.

What makes it strong?

  • It engages specifically with a defined topic — double extortion — rather than ransomware in general.
  • It offers a specific argument — that backup does not address the extortion threat — and develops it.
  • It cites sources and connects the argument to a specific incident.
  • It engages with a contested question — the effectiveness of no-payment policies — and offers a considered position.
  • It contributes an insight — data minimisation as a defence against extortion — that would not otherwise have been in the discussion.
  • It is well-structured and professionally written.

Weak peer response

Great post. I agree that ransomware is a serious problem and that double extortion makes it worse. Thanks for sharing.

What is wrong with it?

  • It adds nothing to the discussion.
  • It contains no analysis or evidence.
  • It is a simple agreement statement — which does not meet the requirement.

Strong peer response

You make a compelling case for data minimisation as a defence against extortion, but I would push back on one aspect of the argument. Data minimisation is easier to advocate than to implement — particularly in regulated sectors where retention requirements are extensive, and particularly where the data at risk includes types (e.g. clinical records) that the enterprise cannot simply delete. This is a real constraint in the healthcare sector, where I work. It might be more accurate to say that data minimisation reduces the value of the data an adversary can steal, but does not eliminate the extortion threat — it just changes the shape of the exposure. I would be interested in whether the evidence supports a stronger or weaker version of your claim.

What makes it strong?

  • It engages specifically with a claim in the peer's contribution.
  • It disagrees respectfully — with reasons, not simply with the assertion of an opposing view.
  • It brings specific experience — the healthcare sector's retention requirements — as evidence.
  • It refines the claim — distinguishing between reducing the value of data and eliminating the extortion threat.
  • It invites further discussion — asking what the evidence supports.

09 Academic integrity

The discussion forums are part of the assessed work of the course. Academic integrity requirements apply to forum contributions as they do to assignments and examinations.

  • Your own work. Your contributions must be your own work. Contributions copied from another source — without citation — are plagiarism, and will be treated as such.
  • Proper citation. All use of others' work — including paraphrasing and summarising — must be properly cited. Cite the sources you use, using an accepted referencing style.
  • No unauthorised collaboration. Collaboration on forum contributions is not permitted. You may respond to your peers in the forum, but you may not pre-arrange responses or coordinate contributions outside the forum.
  • Professional confidentiality. Where you draw on your professional experience, ensure that you do not disclose confidential information — about your employer, your clients, or your colleagues. Where in doubt, abstract the example and remove identifying details.
  • Respectful conduct. Contributions should be professional, respectful, and constructive. Personal attacks, harassment, discrimination, and unprofessional conduct are not permitted.

Suspected cases of academic misconduct will be handled in accordance with the university's academic integrity policy.

Professional confidentiality in discussion

The forums benefit from the diversity of professional experience that students bring. However, professional experience comes with professional obligations — including obligations of confidentiality to your employer, your clients, and your colleagues. When drawing on professional experience:

  • Do not identify your employer, your clients, or your colleagues.
  • Do not disclose confidential information.
  • Where necessary, abstract the example — replacing the specific with the general.
  • Where in doubt, use a documented public case rather than your own experience.

10 Use of AI tools

The use of generative AI tools for discussion forum contributions is subject to the same boundaries as for assignments. The purpose of these boundaries is to ensure that your learning — and your assessed work — reflect your own understanding and your own intellectual effort.

Permitted uses

  • Editing and proofreading. Using AI to check grammar, spelling, and clarity in your contribution before posting.
  • Explaining concepts. Using AI to help you understand a concept — provided you then apply the concept yourself in your contribution.
  • Research assistance. Using AI to suggest search terms or to identify possible sources — provided you then locate and read the sources yourself.
  • Generating counterarguments. Using AI to suggest counterarguments — which you then evaluate yourself and incorporate if appropriate.

Not permitted

  • Generating discussion contributions. Posting AI-generated text as your own contribution, in whole or in part.
  • Generating analysis or arguments. Using AI to produce the analysis, the arguments, or the conclusions of your contribution.
  • Generating citations. Including citations to sources you have not read, or that AI has generated without verification.
  • Responding to peers with AI-generated content. Your peer responses must be your own — they must reflect your own reading and reasoning.

Disclosure

Where you have used AI tools in preparing a contribution, you should disclose the use in a brief note on the contribution (or in a contribution in the forum's meta-thread where one exists):

  • Which AI tools you used.
  • For which purposes you used them.
  • How the output was used.
  • Confirmation that the intellectual content is your own.

Failure to disclose AI use where it has occurred may be treated as academic misconduct.

Why disclosure matters here

The discussion forums are particularly susceptible to AI-generated contributions that appear plausible but do not reflect genuine engagement with the material or with the discussion. When contributions are AI-generated, the discussion is undermined — peers who respond to them are responding to nothing, and the learning that the forums are designed to produce does not occur. Disclose AI use where it has occurred, so that your peers know what they are responding to. Where your contribution is substantially your own, no disclosure is required.

11 Support and resources

Course resources

Scholarly and industry sources

  • Academic journals and conferences — IEEE Security & Privacy, Computers & Security, Journal of Cybersecurity, ACM CCS, USENIX Security, and equivalents.
  • Standards bodies and national agencies — NIST, CISA, ENISA, NCSC, and their equivalents.
  • Industry publications — annual threat reports (Verizon DBIR, Microsoft Digital Defense Report), analyst publications, and the major security vendors' research publications.
  • Sector regulators — financial regulators, health regulators, energy regulators, and their published guidance.

Academic skills support

  • Library services — for help with literature search, with database access, and with source evaluation.
  • Writing centre — for help with academic writing, with argumentation, and with referencing.
  • Study skills support — for help with time management and with discussion preparation.

Contact

  • Course instructor — for questions about the participation brief, about expectations, or about specific forum topics. Contact through Brightspace or at the address provided in the syllabus.
  • Teaching assistants — for questions about the course material and about discussion expectations. Contact details are available in Brightspace.
  • Technical support — for problems with the forums or with Brightspace.

Getting help early

If you have questions about the participation requirements, about expectations, or about the material, ask early — the instructor and teaching assistants are here to help. Where you are unsure whether a contribution meets the requirement, it is better to ask before posting than to discover afterwards that it did not. Where your contribution has been marked lower than expected, ask the instructor for guidance — understanding why a contribution did not meet the standard is the fastest way to improve the next one.

12 Preparation checklist

Use the checklist below to plan and to verify your contributions to each forum. It is not exhaustive, but it identifies the principal requirements.

Before each forum

  • Read the forum prompt carefully.
  • Review the lesson material for the unit.
  • Identify the sources you will cite — at least two or three per initial contribution.
  • Read the sources — do not rely on abstracts.
  • Take notes on the key claims, the evidence, and your own reactions.
  • Decide what you will argue — your central claim.
  • Plan the structure of your contribution.

Initial contribution

  • The contribution is 300–500 words.
  • It engages directly with the forum topic — not with enterprise cybersecurity in general.
  • It demonstrates understanding of the readings.
  • It cites at least two or three sources, correctly.
  • It contributes original analysis — not merely a summary.
  • It links theory to practice — connecting the material to a professional context or a realistic scenario.
  • It is clearly written, well-organised, and free of errors.
  • It is posted within the first half of the unit window.

Peer responses

  • At least two meaningful peer responses.
  • Each response is 100–250 words.
  • Each response engages specifically with a claim in the peer's contribution.
  • Each response adds something — an interpretation, an example, a critique, a connection, a source.
  • Where you disagree, you explain why — respectfully and with reasons.
  • Responses are posted within the unit window.
  • Simple agreement statements are avoided — they do not meet the requirement.

Throughout each forum

  • Return to the forum periodically to read and respond to new contributions.
  • Engage with responses to your own contribution.
  • Where the discussion raises a topic you have expertise in, contribute.
  • Where the discussion is quiet, prompt it — pose a question, suggest a source, share an example.
  • Maintain professional and constructive conduct throughout.

Integrity and disclosure

  • All contributions are your own work.
  • All sources are cited.
  • Professional confidentiality is respected — no identifying or confidential information is disclosed.
  • Where AI tools have been used, the use is disclosed in accordance with the requirements set out above.
  • Conduct is professional, respectful, and constructive.

A final note

The discussion forums are, for many students, the most valuable element of the course. They are the place where the material becomes your own — through engagement, through explanation, through the exchange of ideas with peers who bring different professional experience and different perspectives. They are the place where you develop the professional capabilities that the course is designed to produce — the ability to read critically, to reason clearly, to communicate persuasively, to disagree productively, and to learn from others. Approach them accordingly — as opportunities rather than as obligations.

👤