Linux Security Status on 2017

39
Linux Security 2017 status and AppArmor info. Kazuki Omo( 和毅 ): [email protected] Secure OSS Sig. : http://www.secureoss.jp

Transcript of Linux Security Status on 2017

Page 1: Linux Security Status on 2017

Linux Security 2017 status and AppArmor info.

Kazuki Omo( 面 和毅 ): [email protected]

Secure OSS Sig. : http://www.secureoss.jp

Page 2: Linux Security Status on 2017

2

Who am I ?

- Security Researcher/Engineer (17 years)

- SELinux/MAC Evangelist (12 years)

- Antivirus Engineer (3 years)

- SIEM Engineer (3 years)

- Linux Engineer (17 years)

Page 3: Linux Security Status on 2017

3

Agenda

- Current Linux Security Trend

- Update for AppArmor

Page 4: Linux Security Status on 2017

Current Linux Security Status

Page 5: Linux Security Status on 2017

5

Current Linux Security Status

No one is talking about these Anymore!!

In Japan OSS env...

- How to enforce user to enable SELinux/AppArmor.- Why SELinux is better than AppArmor.- Why you need to enable SELinux/AppArmor….

Page 6: Linux Security Status on 2017

6

Current Typical Linux Security Projects.

- Kernel hardening

- Working with ChipSet

- MAC, Capability, SecComp.

- Userland (Container)

Page 7: Linux Security Status on 2017

Chipset

Page 8: Linux Security Status on 2017

8

ARM

Protect against illicit modification of pointers

Page 9: Linux Security Status on 2017

9

ARM

Page 10: Linux Security Status on 2017

10

AMD

Encrypt for truly separate each VMs.

Page 11: Linux Security Status on 2017

11

AMD

Performance degrade is negligible.

Page 12: Linux Security Status on 2017

12

AMD

Separate HostOS and GuestOS

Page 13: Linux Security Status on 2017

13

TPM2 Support

Trusted Boot / Integrity Mgmt / Log for analyze

Page 14: Linux Security Status on 2017

14

Current Typical Linux Security Projects.

- Kernel hardening

- Working with ChipSet

- MAC, Capability, SecComp.

- Userland (Container)

Page 15: Linux Security Status on 2017

Kernel (Hardening)

Page 16: Linux Security Status on 2017

16

Kernel Hardening

Page 17: Linux Security Status on 2017

17

Kernel Self Protection

Page 18: Linux Security Status on 2017

18

Kernel Self Protection

Page 19: Linux Security Status on 2017

19

Kernel Self Protection

Discussion for Stack Clash

jump

Stack

Stack guard

Page 20: Linux Security Status on 2017

20

Current Typical Linux Security Projects.

- Kernel hardening

- Working with ChipSet

- MAC, Capability, SecComp.

- Userland (Container)

Page 21: Linux Security Status on 2017

Android (Environment)

Page 22: Linux Security Status on 2017

22

ARM

Use Secure boot for integrity check.

Page 23: Linux Security Status on 2017

23

Google

Android: default(hash for integrity check.)

Page 24: Linux Security Status on 2017

24

SELinux in Android Oreo

Page 25: Linux Security Status on 2017

25

SE-Android

SELinux is “already working” on Android.

Mitigating

Page 26: Linux Security Status on 2017

26

SE-Android

Now they are focusing how to easy to maintain.

Page 27: Linux Security Status on 2017

27

SE-Android

Now they are focusing how to easy to maintain.

Page 28: Linux Security Status on 2017

28

Current Typical Linux Security Projects.

- Kernel hardening

- Working with ChipSet

- MAC, Capability, SecComp.

- Userland (Container)

Page 29: Linux Security Status on 2017

MAC, Attack Surface Reducing, etc.

Page 30: Linux Security Status on 2017

30

Access Control

Pre:

Docker(CentOS) → SELinux Enabled

Docker(AppArmor) → AppArmor Enabled

Disable SELinux?

Disable AppArmor?

Page 31: Linux Security Status on 2017

31

Container A

Host OS

Access Control (Stackable LSM)

Container B Container C

How to Mix them. → Stackable

Container/Cloud: Host Env is given by Host-Admin.

Page 32: Linux Security Status on 2017

32

Attack Surface Reducing

seccomp

System call filtering

Page 33: Linux Security Status on 2017

AppArmor Updates

Page 34: Linux Security Status on 2017

34

AppArmor Updates

Stacking LSM / containers

Page 35: Linux Security Status on 2017

35

AppArmor Updates

Policy Namespaces & Stacking

Page 36: Linux Security Status on 2017

Conclusion

Page 37: Linux Security Status on 2017

37

Conclusion

- Linux Security is still growthing.

- Not so much information in Japan.

- We will keep to watching/spreading/contributing.

Page 38: Linux Security Status on 2017

38

Any Questinos?

Page 39: Linux Security Status on 2017

39

Thank You!!!