Link to home
Start Free TrialLog in
Avatar of sunhux
sunhux

asked on

Assessing Alpine linux in terms of security & support

Our apps architect recommends  Alpine Linux for our
microservices/container environment.

Some time back, a patch management vendor told us
that patching for Alpine can't be managed by Satellite
or BigFix  ie we have to manually download & patch.

Q1:
is the above true or is there something like 'yum' in
RHEL to patch Alpine.

Q2:
Also, there's no CIS hardening benchmark nor any
docs that standardize what to harden for Alpine.

Q3:
Architect further points out that Alpine is the most
secure & efficient Linux to use for microservices;
is this true?  Does Alpine has good development
team that constantly check for vulnerabilities &
release advisories/patches (at least like RHEL)?

https://alpinelinux.org/about/
https://en.wikipedia.org/wiki/Alpine_Linux

Q4:
Where can I view past Alpine's CVEs/vulnerabilities
list & how can we assess how good are support
for Alpine?  Don't want a case where we log a
case for support & there's lack of response &
no solution
Avatar of sunhux
sunhux

ASKER

From cyber perspective, I have concerns below:

a) As Alpine is rare, how many agents esp SIEM agents (Splunk,
    Alienvault, Trustwave/Spiderlabs) could install on it or this
    is irrelevant as it's the Base OS (we use RHEL) that matters?

b) in terms of virtual patching, I may want to use Trendmicro
    Deep Security but DS agents dont install on Alpine or we
    just need to install on Base OS & not the Container instances
    /image?

c) Possibly other agents like backup (or this doesn't matter as
    we backup the image?) & other tools that we may want to
    install agents in future??

d) Refer to the Wiki link above: each Alpine release lasts only
    about 2 years, very short lifecycle while RHEL (or CentOS
   as well) lasts 4-5 years usually: so we'll have to keep tech
   -refreshing Alpine every 2 years or is tech-refreshing
   Alpine in container environment is a trivial task?

e) Anyone has encountered penetration (blackbox or greybox
    or apps pentest) in Alpine environment & how easy it is to
    fix?  With an endpoint IPS, I can close many XSS & other
    findings more easily
SOLUTION
Avatar of David Favor
David Favor
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of sunhux

ASKER

Q1:
Ok, Alpine has apk.  Suppose we want something like Satellite or
only permit 1 Alpine to pull patches down into a repository & the
rest of the Alpine in our set-up gets their patches from this
repository, does Alpine offers anything of this nature?

Do we pay subscription to get Alpine support like the way we pay
subscription to RedHat & if so, is Alpine's support/subscription
 fee based on per Alpine endpoint?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of sunhux

ASKER

Item c  is quite crucial: regulators & auditors require PAM (eg: Cyberark,
Thycotic, TPAM) whenever there's privileged access.

Reckon the 3 PAM  I indicated above requires their agents to be installed
in the endpoint without which, it won't work or there's no agent required?
We won't get past our regulators (2 of them) & auditors without a PAM.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
As noci suggested, if you really require Alpine (you haven't explained why yet), you'll dig into each question by install Alpine + testing.
Avatar of sunhux

ASKER

David, it's the apps architect's
recommendation n I'm still
brainstorming with him.

Have seen a site showing Intel's
CleanLinux offers best performance while Alpine
is below average relative to
other distros like Debian,
CentOS, Ubuntu
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
noci actually said this more clearly than my rambling.

Support, to me, is always my first consideration which dictates I use Ubuntu.

If upstream support is flawed, this means project time/budget overruns occur, which is unacceptable with tightly controlled projects.

noci also provides clarity about I/O. If you use a VM based system of any kind, you'll do 2x or more I/O for every 1x I/O, which is a performance killer. This is why I only use LAMP stacks running in LXD containers, so all processes run at bare metal speed.

Still be best if you open a 2nd question describing your project specifics, asking for design suggestions.

Or hire 10x smart people for 1 hour of consulting. Have each person design your system for you. Roll in the best of all the design suggestion, into your final design.
You're welcome!

Tip: Whether you use Docker or LXD depends heavily on your application.

1) Microservices (with no persistent data across boots) use Docker.

2) Websites/Apps (requiring any persistent data across boots, like MariaDB/MySQL) use LXD.

If you violate this, for example trying to use Docker to implement a LAMP Stack, you must first redevelop some ad-hoc LXD like data management system for your SQL data files, which will be far more fragile than LXD.

Be sure to use the correct tech for your project.

Suggestion: Open another question... maybe titled... "LXD or Docker for project"... then describe your project + ask for design assistance.