Opened 8 years ago

Closed 4 years ago

#1685 closed task (complete)

Document and test security procedures

Reported by: shane Owned by:
Priority: high Milestone: Kea1.0
Component: Unclassified Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

We need to write down how we handle security bugs discovered in BIND 10.

Subtickets

Change History (5)

comment:1 Changed 5 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:2 Changed 4 years ago by tomek

  • Milestone changed from Remaining BIND10 tickets to Kea1.0
  • Priority changed from medium to high
  • Version set to git

Due to our upcoming business arrangements, this becomes both imporant and urgent, thus moving to 1.0 as high.

This involves more than just documenting, make sure that all procedures are implementable.

comment:3 Changed 4 years ago by tomek

  • Milestone changed from Kea1.0 to Kea1.0-beta

Milestone renamed

comment:4 Changed 4 years ago by tomek

  • Milestone changed from Kea1.0-beta to Kea1.0

comment:5 Changed 4 years ago by tomek

  • Resolution set to complete
  • Status changed from new to closed

We did complete our first security incident handling, and did a post mortem. The procedures were updated accordingly. Closing ticket as discussed on 2016-01-07 meeting.

Note: See TracTickets for help on using tickets.