1 of 24

ECS 188: Ethics

Final paper and final presentation

2 of 24

Administrative

Last time: The Moral Character of Cryptographic Work

This time: Nothing!

Next time: Bad Company -- Facebook edition

Final report due on 5/30

In class presentations starting on 6/1

3 of 24

Extra office hours for practice talks and feedback on your final paper!

Adding extra office hours for next week

  • Wednesday, May 30th: 10am-noon
  • Wednesday, May 30th: 1-3pm

Will not give feedback on half-baked talks, needs to be somewhat polished already

4 of 24

Final project grading rubric

Final report: 20 points

5 points: Explanation of technology in question

5 points: Explanation of the Ethical issues with that technology

5 points: Depth of research

5 points: Organization, flow, grammar, style, etc

5 of 24

Include a section on technology itself!!!!!!

Final report: 20 points

5 points: Explanation of technology in question!!!!!!!!!!!!!!!

5 points: Explanation of the Ethical issues with that technology

5 points: Depth of research

5 points: Organization, flow, grammar, style, etc

6 of 24

Final paper outline

One way to do it -- mirror the flow of your intro

Introduction

Technology

Ethical question

Details of both sides

Conclusion / your opinion

References

7 of 24

Reminder -- you need to use my LaTeX template

8 of 24

In class presentations

Assigned groups randomly to in-class presentation slots

8 minutes to present -- no questions

4 minutes for Q&A (12 minutes total)

Expect some difficult questions

During Q&A the next group needs to setup

9 of 24

Class presentations

Attendance is mandatory for all lectures where students are presenting work

You must be on time and not leave

You must ask at least one question

Grade breakdown:

  • 12 points for the presentation
  • 8 points for attendance + asking at least one question

10 of 24

Presentations

Goal: get people excited about your research

  • Convince them to read your paper
  • Not to explain how it works in detail

11 of 24

Presentation suggestions

Don’t have a series of text bullet points!!!!

  • Figures are your friend!
  • A few text bullet points are fine

Rule of thumb, more slides with figures that slides with text

Don’t jam too much info into one slide

12 of 24

Outline for a talk -- intro (4-5 minutes)

Problem / technology

Introduce the ethical question

Preview of one side of the debate

Preview of the other side of the debate

Just enough detail so that they’ll pay attention for the rest of the talk

Overview of talk -- 1 slide

13 of 24

Outline for a talk -- body

Focus on one or many of the sides of the ethical question

Your goal is for people to get a full picture of the issue at hand

I encourage you to find short video clips or other material to backup your arguments

Conclude with your opinion and why you chose this

14 of 24

After the talk, Q&A

By far the most difficult part

Will sometimes have to deal with questions based off of misunderstanding of your talk

Good approach -- enter a dialog with the person

  • Personal connection
  • Agree on the question before trying to answer
  • Gives you time to think of an answer if needed !

Can also reflect to a better sounding question, but this can be risky if not handled well

15 of 24

Advice

Be excited about your research

Lots of practice

Write down questions that come up as you practice

Script first two sentences

Lots of figures

16 of 24

An example of a good intro

17 of 24

An example of a good intro

For an example of bad slides, see the previous 10

18 of 24

Building secure systems

  • We make assumptions designing secure systems
  • Break secure system, break assumptions
    • E.g., look for crypto keys in memory
  • People assume hardware is correct

  • What if we break this assumption?

18

19 of 24

Hardware as complex as software

19

20 of 24

Malicious hardware

20

HW

Circuit designed

21 of 24

Malicious hardware

21

HW

HW

Circuit designed

Attack inserted

22 of 24

Malicious hardware

22

HW

HW

HW

Test cases

Test cases

Circuit designed

Attack inserted

Suspicious circuits �identified and removed

Design Time

23 of 24

Malicious hardware

23

HW

HW

HW

HW

Test cases

Test cases

BlueChip

BlueChip

Circuit designed

Attack inserted

Suspicious circuits �identified and removed

Hardware triggers �emulation software

OS

Design Time

Run Time

24 of 24

BlueChip run time HW and SW make forward progress

24

HW

BlueChip rem HW detection

BlueChip emul. software

OS

BlueChip software emulates around removed hardware

BlueChip hardware detects inconsistent states