Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Developers and Security Teams Under Pressure to Collaborate
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
tdsan
50%
50%
tdsan,
User Rank: Ninja
7/15/2019 | 3:58:36 PM
Re: spot on especially for container security


Out of the things mentioned in this article, they did not talk specifically about how it could affect IT Security/CyberSecurity. However, we could infuse the topics covered with CyberSecurity to Create Definitions -> Perform Data Extraction -> Data Classification -> Predict Historical Significance -> Pattern Recognition -> Regression Testing -> Predective Analytics; these areas of study can help to create an algorithm or policy to impede possible attacks. The items listed (applications to be used for ML) can be used to mitigate potential threats. The TIM (Threat Intelligence Machine) goes through a specific process that can be applied in numerous areas of IT, review the flow chart listed below:



Todd
pawan.shankar
50%
50%
pawan.shankar,
User Rank: Author
7/15/2019 | 2:54:05 PM
Re: spot on especially for container security
good call on the ML, I just wrote about why ML is a good fit for container security, https://www.darkreading.com/cloud/is-machine-learning-the-future-of-cloud-native-security/a/d-id/1335206
tdsan
50%
50%
tdsan,
User Rank: Ninja
7/15/2019 | 1:05:18 PM
Re: spot on especially for container security
Yes, agreed, we need to improve the application imaging process where the app is locked down using a Pentesting process and an app policy needs to be activated when referring to the internal functions, characteristics and outcomes should be studied so a policy change can be put in place to mitigate organizational problems:
  • "yum install selinux; systemctl enable selinux; systemctl state selinux" # Install, enable and verify state
  • "grep -i avc /var/log/audit/audit.log | audit2allow --module local > local.te" # Create module for something specific, review the policy, I am looking the web traffic since this is a web server
  • "yum install policycoreutils-devel" # Gives users the ability to configure policies from the desktop
  • "find / -name "local.te" print0 | xargs -0 -t semodule -i" # looks for local.te and installs it as one of the modules
  • "setsebool -P httpd_read_user_content" # Sets the policy permanently to read pages that have been served up by nginx or apache

There are other application programming aspects that we can review but this gives the user an idea of how a developer and security consultant can work together to manipulate the characteristics of files, filesystem, domains, policies, and executables.

Todd
tdsan
50%
50%
tdsan,
User Rank: Ninja
7/11/2019 | 12:15:12 PM
Re: spot on especially for container security
I agree with the points you made, I do think containers are the way, in addition:
  • SELinux - we need to work with the security teams and DevOps team to secure the application, filesystem, domain, executable/bin and application characteristics
  • "setenforce 1; reboot; getenforce; yum install nginx; systemctl start nginx; semanage fcontext -a -R 'httpd_sys_context_t' '/usr/share/nginx/html(/.*)?'; setsebool -P http_read_user_content 1; semanage port -a -t 'http_port_t -p tcp 80,443 (this will limit what the external user has access to)"
  • "iptables -I INPUT 1 -p tcp -m multiport --dport 80,443 -m conntrack --ctstate NEW -j ACCEPT"
  • "for i in `rpm -qa | grep apache`; rpm -e $i ; done #(remove apache from the system (nginx is installed now)"
  • "Docker configuration - yum install docker; systemctl start docker; docker login <enter user from docker hub>; docker pull nginx; docker run -p 8082:80 --name nginx2 -v $PWD:/usr/share/nginx/html/docs --restart unless-stopped nginx # this creates a docker container on your linux machine running nginx latest image or richarvey\nginx-php-fpm # works well using secure https" 
  • Firewall - we need to start utilizing NGFW where the FW is able to think and look at the application's heuristics and understand the application. If there is an outside variant (i.e. Ransomware) and it activates encryption tools, the NGFW (onboard or external) needs to put that process in a container or isolate that process where its effects are limited, what can DevOps do to work with the Security teams to create a pre and post scenario when it finds this type of attack (collaborate to resolve this issue)
  • ML - Machine Learning is missing from this equation but with the DevOps teams help by using Tensorflow techniques, we can train the ML aspect of the application to look for anomalies and variants (especially those that access ssh/keys over the internet after numerous attempts)

Todd
pawan.shankar
50%
50%
pawan.shankar,
User Rank: Author
7/8/2019 | 11:11:54 AM
spot on especially for container security
this seems to be very applicable in the container security space, where devops and security are traditionally in different silos. Teams need to work closer together and the pressure to collaborate is increasing in order to not sacrifice agility for security and vice versa.
tdsan
50%
50%
tdsan,
User Rank: Ninja
6/29/2019 | 1:51:43 PM
Re: Control
Interesting, I do think it depends on the type of work they are performing. If someone from the security team can review the code to determine if the code meets 'CMMI' coding best practices at the beginning of the Agile scrum development process, then yes I agree but that is dependent on the level of compentency the security team has when it comes to "SecDev" or the "Security Development process.
However, in most cases, security groups don't have coders on the team with a strong background in security, so I do think this aspect of the industry is evolving, by combining these business areas, in the long-run it will benefit the industry.

Todd
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/28/2019 | 6:35:23 PM
Control
If a dev team can handle 80% of security work, he added, it's helpful to the development process. This is the case in most of the situations but it can be managed.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/28/2019 | 6:31:57 PM
Trade-off
There's a tradeoff between depth and speed This is really true. Balancing act.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/28/2019 | 6:30:27 PM
Cloud
DevOps evolved along with the cloud, driving the speed of new software releases and requiring security to review applications more frequently. Agree. Cloud made it more possible to engage security team early enough, as they enforce certain rules from the beginning.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/28/2019 | 6:28:32 PM
Re: SecDev - wave of the future
We will be incorporating "SecDev" or "Security Development" teams into our environment as well and thank you for this valuable insight. Agree this will be important in short and long terms.
Page 1 / 2   >   >>


Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
Sodinokibi Ransomware: Where Attackers' Money Goes
Kelly Sheridan, Staff Editor, Dark Reading,  10/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18217
PUBLISHED: 2019-10-21
ProFTPD before 1.3.6b and 1.3.7rc before 1.3.7rc2 allows remote unauthenticated denial-of-service due to incorrect handling of overly long commands because main.c in a child process enters an infinite loop.
CVE-2019-16862
PUBLISHED: 2019-10-21
Reflected XSS in interface/forms/eye_mag/view.php in OpenEMR 5.x before 5.0.2.1 allows a remote attacker to execute arbitrary code in the context of a user's session via the pid parameter.
CVE-2019-17409
PUBLISHED: 2019-10-21
Reflected XSS exists in interface/forms/eye_mag/view.php in OpenEMR 5.x before 5.0.2.1 ia the id parameter.
CVE-2019-10715
PUBLISHED: 2019-10-21
There is Stored XSS in Verodin Director before 3.5.4.0 via input fields of certain tooltips, and on the Tags, Sequences, and Actors pages.
CVE-2019-10716
PUBLISHED: 2019-10-21
An Information Disclosure issue in Verodin Director 3.5.3.1 and earlier reveals usernames and passwords of integrated security technologies via a /integrations.json JSON REST API request.