Transforming Information Security Optimizing Five Concurrent Data Trends To Reduce Resource Drain Kathleen M Moriarty instant download
Transforming Information Security Optimizing Five Concurrent Data Trends To Reduce Resource Drain Kathleen M Moriarty instant download
https://ebookbell.com/product/transforming-information-security-
optimizing-five-concurrent-data-trends-to-reduce-resource-drain-
kathleen-m-moriarty-42281032
https://ebookbell.com/product/data-and-mobility-transforming-
information-into-intelligent-traffic-and-transportation-services-
proceedings-of-the-lakeside-conference-2010-1st-edition-roland-
tusch-4194486
https://ebookbell.com/product/visual-tools-for-transforming-
information-into-knowledge-second-edition-costa-11804020
https://ebookbell.com/product/visual-tools-for-transforming-
information-into-knowledge-hyerle-59503758
https://ebookbell.com/product/transforming-healthcare-through-
information-systems-proceedings-of-the-24th-international-conference-
on-information-systems-development-1st-edition-doug-vogel-5483826
https://ebookbell.com/product/the-information-revolution-transforming-
the-world-through-technology-1st-edition-tamra-b-orr-51654066
https://ebookbell.com/product/introduction-to-information-
visualization-transforming-data-into-meaningful-information-gerald-
benoit-10417076
https://ebookbell.com/product/public-sector-reform-using-information-
technologies-transforming-policy-into-practice-thanos-
papadopoulos-2360188
https://ebookbell.com/product/the-impact-of-building-information-
modelling-transforming-construction-ray-crotty-4155562
TRANSFORMING INFORMATION
SECURITY
Optimizing Five Concurrent Data
Trends to Reduce Resource Drain
KATHLEEN M. MORIARTY
Dell Technologies, USA
1 Interconnected Trends
2 Board-level Program Evaluation and Guidance
3 Architect a Secure Network with Less
4 Encryption
5 Transport Evolution: The Encrypted Stack
6 Authentication and Authorization
7 The End Point
8 Incident Prevention, Detection, and Response
9 Looking Forward
References
Index
Preface
Looking 5 to 10 years forward, to an ecosystem with end-to-end
encryption, network architectures and hence security as we know it
in enterprises will be transformed. The protocols for end-to-end
encryption have been developed, but the management of security
and networks have not caught up.
This is an opportunity to think strategically on the design of
network architectures, the placement and use of management tools,
and to plan for resources, especially the hard-to-find security
practitioner.
Let's face it, information security is much more difficult than it
needs to be, and this transformational period for protocols should be
seen as an opportunity to fix these issues. The focus on this forward-
looking strategic view is primarily considering the tremendous deficit
in information security professionals will never be filled through
training. The current set of security solution architectures involving
middleboxes are geared toward the top 1% of organizations that can
afford to hire multiple information security professionals. The other
aspect of this strategic vision includes the goal of a truly improved
and intrinsically more secure network environment. Envision a fully
encrypted and authenticated network with functions better performed
at scale where collective knowledge is strategically and carefully
applied. As it has come to be an acceptable outcome in the Internet
of Things (IoT) space, envision elemental services from end point
vendors to prevent, detect, and thwart threat actors leveraging
collective knowledge on patterns and behaviors through the use of
artificial intelligence and machine learning applied back to your
systems to better scale incident detection and response.
This means no middleboxes that each require a full-time
employee to manage. A reliance on information collected at the
edge, or end point systems, as well as streams provided to these
systems to prevent or block known threats would be managed by a
smaller group of expert analysts with large swaths of data to make
assessments. Vendors could provide services to prevent and resolve
security issues on their applications and platforms in aggregate
utilizing a small number of analysts specific to their technologies and
threat landscapes. This already happens in hosted environments,
but perhaps not in the ways this long-term vision moves us toward to
further reduce human resource impacts. Gradually, this would all
give way to intrinsically secure applications and the ability for users
to better manage their personal data. Let's start with a few relevant
examples that scale security and incident management well, and
then the book will expand from there more broadly setting new
architectural patterns that scale.
The APWG [APWG] hosts central repositories around use case-
specific threats. This example is on the antiphishing repository.
Anyone can contribute to this antiphishing repository containing
attack-related information including web service links (URLs) with
known malware, compromised email servers, etc. The information is
used, verified, and updated by participating organizations, like RSA
who engages law enforcement to take appropriate legal action and
have malicious sites removed from the Internet. Where this gets
interesting in terms of scale is the use of the information sources by
programs like Google Safe Browsing [Google, 2019]. This particular
program assesses threats and integrates deny lists into the browser
that are updated on a periodic basis throughout the day. Additionally,
this is used as a plugin for every other major browser, greatly
reducing the number of analysts needed to have a large impact on
threats for just about every browser user on the planet, as an
individual or within a corporate network benefiting.
Turning to the payment processing industry, threat detection
occurs at the issuing bank, which is part of the payment processing
flow that begins with the point of sale at millions of retail locations as
well as online commerce sites. In this case, transactions are stopped
at the point of sale or prior to the transaction being completed. In
terms of scale and location of intelligence, this makes sense except
for smaller issuing banks that may not have the fraud detection
capabilities of larger organizations. The issuing bank has full records
of card users' trends and patterns and can detect unusual behavior.
The point of sale is able to verify whether or not your credit card is
valid and has adequate funds to proceed with a transaction.
If you peel back this example a bit, there are providers of data
that aid in fraud detection to further narrow the number of experts
needed to detect threats. Fraud information services provide lists of
compromised accounts and credit cards to the appropriate issuing
bank, culled from the dark web. This compliments the work
performed by issuing banks to detect fraud. Financial institutions
also collaborate on threat detection, but not necessarily fraud
detection techniques. There is room for improvement in each of
these examples; however, they demonstrate collaboration between
enterprises and vendors to protect enterprise users and individuals
with fewer overall human resources. For some types of threats,
solutions still do not scale and near-term work could help to reduce
the number of analysts needed with architectural model changes
with an eye toward efficiency given today's resource constraints.
Longer term, methods will emerge to prevent the attacks and thus
reducing the need for defenses like these. Threat detection is just
one area this book examines as it unfolds to map out security
architectures to improve security and reduce human resource
requirements for organizations of all sizes. It is imperative that we
think toward new architectural patterns including ways to prevent
such attacks now as protocol design changes and technology
advancements enable this transformation.
Acknowledgments
The research for this book began during Kathleen's two terms as an
Internet Engineering Task Force (IETF) Security Area Director,
March 2014–2018, reading all Internet drafts prior to publication. The
text was independently produced while working in the Dell EMC and
DELL Technologies Office of the CTO with permission. Proof of
Concept and development to test hypothesis were performed by
several of the DellEMC Office of the CTO Dojo teams and one by the
USC supported by the DoD through the Hacking for Defense
Program.
A tremendous thank you to Chris Inacio; his careful proofread of
the contents looking to catch technical errors or areas that could
benefit from further explanation. Special thanks to technical
reviewers Spencer Dawkins and Rick Martinez who also aided in
improving the book. Thank you to Nicole Reineke for your proofread
and suggestions. Thank you to John Roese, Ken Durazzo, Frederic
Lemieux, and Rowland Shaw for supporting my work and
development of this book on security transformation. Gratitude also
for those who helped validate the theories and projected evolution
path including Rob Adams, Dennis Moreau, and Liam Quinn.
A tremendous thank you to the fabulous Dojo teams and
business unit architects at Dell Technologies. I am forever grateful
for the opportunity to work with each team member in collaborating
and testing out some theories in proof of concept development work.
Dojo team members who implemented and developed additional
ideas around proposals include Omar AbdulAal, Himanshu Arora,
Shary Beshara, Gus Cantieni, Xuebin He, Akshaya Khare, James
King, Omar Mahmoud, Lauren Marino, Amy Mullins, Megan
Murawski, Thinh Nguyen, Xavier Nieves, Ahmed Osama, Alex
Robbins, Seth Rothschild, Ben Santaus, Amy Seibel, Mohamed
Shaaban, and Yuzhi Xiao. Thank you to security colleagues for your
collaboration on several projects themed around scaling security
management and helping to push the envelope with the goal of
improving overall security for customers. Colleagues include Sachit
Bakshi, Rudy Bauer, Travis Gilbert, Nicholas Grobelny, Samant
Kakarla, Rick Martinez, Amy Nelson, Michael Raineri, and Charles
Robison. Thank you to numerous colleagues in the IETF for your
work and meaningful conversations to advance security.
Thank you to my dear son, who is an all-around wonderful child. I
am grateful for all the mornings you slept late, giving me time to work
on this book.
1
Interconnected Trends
There are at least five trends, when interconnected, that have the
potential to result in a dramatic shift in how information security is
managed today, for the better. Within each trend, there are some
inevitable outcomes as well as interdependencies with other trends
that are not often considered together to better map out a forward
path. The trends include:
increased deployment of encryption,
strong session encryption, preventing interception,
transport protocol stack evolution,
data-centric security models, and
users control of data.
While much work is happening within each trend, these trends
are not typically all considered together. To realize positive change
and reduce the overall threat space, it is imperative that we do just
that. This chapter will explore each of the trends and how they
interconnect to set the stage for the proposed changes and deeper
technical considerations discussed in the book as the trends are
embraced. The increased deployment of strong encryption supports
data-centric architectures and is contributing to the transport protocol
stack evolution. User control of data is a desired outcome for those
looking to protect user’s privacy; however, work to support this trend
is at an early stage. The general theme of the inability to manage
information security as it is architected today, due to insufficient
resources, will be explained detailing how embracing these trends
and new architectural patterns improve efficiency and reduce
resource requirements.
1.1 Increased Deployment of Encryption
While the Snowden revelations (Gidda, 2013) starting in June 2013
led to an immediate increase in deployed session encryption, trends
in standards development also shifted. The fundamental shift in
standards was driven by the acceptance of less-than-perfect security
in favor of deployability, leading to a sharper increase in deployed
encryption starting around 2017. Examples of this include
Opportunistic Security (Dukhovni, 2014) and the Internet
Engineering Task Force (IETF) Automated Certificate Management
Environment (ACME) (Internet Engineering Task Force, 2020h).
Opportunistic security enables an upgrade path from clear text
sessions to sessions encrypted without authentication, to
authenticated session encryption. It is important to note that
opportunistic security is breakable, but allows for easy automated
configuration without knowledge of the other endpoint. Prior to this
shift, such efforts would not have gone anywhere since the
unauthenticated session could be intercepted, leaving you with no
security. From a purist point of view, that was not acceptable in the
past, but now there's a justification. Opportunistic security raises the
cost for pervasive monitoring, resulting in an in-feasibility to monitor
all sessions passively. If nation states or malicious actors want to
monitor traffic in this model, specific sessions would be targeted for
decryption and observation.
While we haven't seen much deployment outside of opportunistic
security use with IPsec (Internet Engineering Task Force, 2020d),
automated certificate management is enjoying huge success via the
Let's Encrypt project. Sessions not previously encrypted have used
ACME via Let's Encrypt to automate the management of certificates,
improving privacy protections for end users. While Let's Encrypt
offers certificates for free, the ACME protocol can be used by other
certificate providers who are interested in automating maintenance
of certificates, including any type of certificate. An out-of-band
process may be required for identity proofing of individuals and
organizations for Extended Validation (EV) certificates or other
certificate types. If you are not already using ACME, it should be
considered a way to ease certificate management and say goodbye
to the days where an expiring certificate causes extensive server
outages without anyone realizing the root cause. Now, with
automation needless downtime due to certificate management
problems can be avoided.
The initial increase of deployed encryption on the web rose to
around 30% in 2014, the year following Snowden revelations.
ACME's automation and free certificates from the Let's Encrypt
project helped that number climb to 85% in 2020 (Let's Encrypt,
2020) (Fig. 1.1).
Source: https://letsencrypt.org/stats/
Fig. 1.1. Percentage of Page Loads Over HTTPS by Region.
This trend of pervasive encryption will continue now that session
encryption is easier to deploy and there's ample motivation.
1.2 Strong Encryption
End user privacy, human rights protections, and prevention of
protocol ossification are the primary drivers for the trend
strengthening transport protocol encryption. Encryption is being
designed to prevent interception and limit the exposure of previously
exposed meta-data. When considering end user privacy, it's not only
session content that can reveal sensitive information, but also meta-
data. Meta-data and session signaling information may enable
tracking of user sessions across the network with any identifier or
combined set of unique data that can identify the communicating
parties. The meta-data of the communication session may provide
insight as to the two parties communicating (hostname and Internet
protocol information), length of the session, amount of data
exchanged, possibility of identifying encapsulated protocols, and
types of data exchanged.
Privacy considerations for the end user have been a major driver
for the increased deployment of strong encryption and a reduction in
availability of session meta-data. Transport architects and engineers
are grappling with the go forward options to manage networks in an
encrypted world. There has been some work to catalog the usage of
data and meta-data and the goals of the monitoring performed prior
to this shift in encryption (Moriarty & Morton, 2018). This impact is
felt more by the enterprise than service providers as shown with a
slower move toward adoption of strong encryption.
Transport layer protocols using provably secure strong encryption
began to emerge in 2018. Deployment may have more limited
success in environments where data is expected for monitoring (e.g.,
within the enterprise) near-term, the research from the cited survey
indicates that deployment of these protocols should not suffer on
Internet bound connections. The reason for this is that service
provider monitoring is typically limited to the available protocol
header information at the transport protocol, network, and link layer.
These header fields will continue to be available with the current set
of emerging transport encryption protocols including Transport Layer
Security (TLS) version 1.3 (Rescorla, 2018), QUIC (Internet
Engineering Task Force, 2020e), and TCPcrypt (Internet Engineering
Task Force, 2020g).
A goal for an end-to-end encryption protocol is that the session
initiates at the client application (web browser, streaming video
application, etc.) and terminates at the server destination, thereby
protecting the session across the entire transit of the network. In
reality, the session likely terminates at a load balancer instead of a
web server and may include some inspection at this point of
termination. The load balancer termination point may be considered
the server end point in today's web server architecture schemes. If
there are additional servers, including application servers, content
servers, databases, etc. used to deliver the return session content to
the end user or client, there may be additional encrypted streams
established from the terminating load balancer to these other
systems and applications. The subsequent sessions may or may not
use the same encryption protocol as the initiating transport
encryption protocol of the client. A simplified illustration is provided in
Fig. 1.2.
Fig. 1.2. Edge Termination to Data Center.
Internet bound sessions have different security and privacy
considerations from those within a data center, hence the possible
variance on protocol selection for sessions within a data center from
Internet bound sessions. For instance, human rights considerations
in protocols (ten Oever & Cath, 2017) include many existing security
and privacy controls, but add anonymity and pseudonymity as
important to the design for end user protection. Users shouldn't have
to fear for their safety when performing research on health-related or
other similar queries that may be restricted or prohibited in some
regions. When speaking on a panel in Geneva, organized by the
Internet Society in 2015, another panelist told his story where he
wanted to do research on the pros and cons of circumcision in his
country in Africa, but was fearful for his life due to regional beliefs on
this practice. This is just one of hundreds of examples where human
rights considerations are sometimes factored into protocol design.
The drivers are important as is the trend of increasing design and
deployment of strong transport encryption. The threat landscape has
evolved beyond basic confidentiality for information security to
include protection from session interception (passive or active
hijacking), user privacy, and human rights considerations partly due
to pervasive monitoring of governments.
1.3 Transport Protocol Stack Evolution
It seems to me that we're morphing into a really
interesting protocol stack, where UDP is the
transport protocol but QUIC is the REAL transport
protocol, and IPv6 is the networking protocol, but
GENEVE is the REAL networking protocol.
Spencer Dawkins, IETF Transport Area
Director 2018.
The transport stack is evolving, partially a result of the need to
develop and innovate Internet transport in response to the
proliferation of middle-boxes that intercept and sometimes modify
existing well-deployed protocols. End-to-end transport encryption
helps toward this goal. Application developers are highly motivated
in this push for strong encryption to allow for innovation in protocols
supporting their applications. This is one reason why the protocol
stack evolution starts from the application layer encryption protocols
in addition to that being the point in the stack to protect end user
data in transit. To be explicit, TLSv1.3 and QUIC are a couple of
protocols driving the work of transport and routing engineers at lower
layers for this now necessary protocol stack evolution.
The use of UDP and strong transport encryption is an attempt to
address the ossification of existing network protocols and allow for
innovative end-to-end protocol development.
TCP based applications are often intercepted and
sometimes modified by middle-boxes. UDP has not
been intercepted in general, having been deployed
for connectionless query/response applications like
DNS in the past,
Spencer Dawkins.
Performance benefits have been noted with applications using
UDP and QUIC as a result. Through research, instances where UDP
has been rate limited has been discovered as high usage may be
interpreted by a middle-box as a DoS attack. Simply phrased, if
traffic is not intercepted, the end points are free to evolve the
protocol without fear that any update could cause the protocol to be
blocked in its path. If the use of UDP is fully encrypted, including
signaling information, packets cannot be modified in transit.
This all sounds very positive in that protocols may continue to
evolve and protocol designers can be innovative in their solutions
while protecting the privacy of end users. While those are both
laudable goals, this leaves open questions for transport protocol
engineers who focus on congestion control, performance, availability,
and other traffic and operations management tasks that rely upon
header information that has been available in transport protocols to
date. Herein lies the tussle that has become a bit of an arms race
between application developers who can evolve their protocols more
easily if transport remains intact and the management of networks
that has relied on visibility into packet streams to perform network
and security management. For service providers, the visibility has
been limited to publicly available transport, network, and link layer
packet header data (Moriarty & Morton, 2018).
In terms of active development in transport protocols,
development has been limited to UDP for transport in recent years in
an effort to prevent protocol ossification. QUIC is one example that
uses UDP as a substrate. QUIC is an encrypted transport protocol,
using TLSv1.3 secure handshake for authenticated key exchange
intended for real-time or latency sensitive applications (e.g.,
streaming media, gaming, and VoIP services). Google runs QUIC
between Google services and Chrome browsers and is gaining
adoption elsewhere (Jan, 2018). For the enterprise, the business
justification to allow QUIC into networks has not yet been made.
While deployments like that at Google exist and are likely to expand,
the use cases for the QUIC protocol are limited at the moment.
When speaking at RSA Conference and Dell Technologies World
2018, attendees said who were aware of QUIC were outright
blocking it from their enterprise networks. There was no perceived
business imperative for many enterprises to allow QUIC, limiting
deployment. Increased use of streaming protocols to facilitate
business calls may tip the balance in the near future for the
performance gains, improving call quality. Having said that, QUIC
does allow for protocol innovation and evolution and we will continue
to see standard efforts pushing for increased encryption of signaling
information as well as packet payloads to combat the protocol
ossification problem.
Transport engineers, operators, and network managers are
looking for options lower in the stack to ensure the monitoring
functions performed to manage traffic may continue. There are a few
paths in exploration right now with no clear winner. In my opinion, the
simplest and most likely to be deployed option is IPv6 (Deering &
Hinden, 2017) with packet header information such as the Flow
Label (Amante, Carpenter, Jiang, & Rajahalme 2011) and the
Destination Options Header extension (Elkins, Hamilton, &
Ackermann, 2017). The challenge with this option is that global
deployment of IPv6 was at about 25% in 2018 (Internet Society,
2018), although increasing, more work needs to be done. This is a
viable option because many systems now support IPv6 without any
work needed by the end user, including mobile devices. Another
challenge with IPv6 is that the header extensions are sometimes
dropped by middle-boxes (Gont, Linkova, Chown, & Liu, 2016).
Interoperability testing on the recent IPv6 revision in RFC8200
(Deering & Hinden, 2017) should help to close this gap. This update,
an interoperability testing, ensures header extensions are an
expected part of the standard, reducing the rate packets are dropped
since the results posted in 2016 [RFC7827]. While the Hop-by-Hop
header extension may seem like another possibility, it has some
issues as cited in RFC8200 Section 4.8. This extension may be
modified at hops along the path, unlike the Destination Options
header that is meant for end-to-end usage that may trigger the use
of a slow processing path.
Alternatively, there has been a proposal from several well-
respected transport engineers in the IETF to add a layer to the stack
for measurement. “A Path Layer for the Internet: Enabling Network
Operations on Encrypted Protocols” (Kuhlewind et al., 2017)
describes the network ossification that has led to the increased use
of encryption along with their solution to add a path layer called, Path
Layer UDP Substrates (PLUS).
The obstacles to implement and deploy this additional protocol
layer with useful packet headers for measurement may be quite
high. Considering IPv6 headers have experienced difficulty at
middle-boxes after 20 years of existence as a standard, it is likely
that the path to deployment for something like PLUS would be quite
difficult.
The PLUS work has been presented at IETF meetings and has
failed to move forward due to privacy concerns and the possibility of
revealing information about the end user. While some of the same
Another Random Document on
Scribd Without Any Related Topics
CHAPTER XXI
Magnificent Country
T HERE was a rocky hill not far away, and it was Joe who
expressed a desire to go over and climb to the top.
“Fairly high,” he remarked. “Ought to be able to get a good view
of the surrounding territory.”
“Yes,” Bob agreed. “Maybe we can catch sight of an Indian
village in the distance. The unknown tribe! Be fine if we could be the
ones to locate it, wouldn’t it?”
“Sure would. Professor Bigelow would be delighted beyond
words. Think of the rumpus he’d kick up if we announced that we’d
found the savages he’s been hunting.”
It was a distance of less than a half-mile to the foot of the knoll,
and the youths made it in a very few minutes. Then they began the
task of climbing the jagged side. There was little vegetation to
hinder their progress, although twisted vines and shrubs were rather
numerous on the ground.
“The undergrowth offers footholds that we could not otherwise
find,” said Bob. “Here’s a place where it comes in handy, even
though most of the time it’s merely something to avoid.”
At last, panting and perspiring, the youths reached the top of
the hill and then turned to glance down below. Jungle, jungle,
jungle! Nothing but heavily wooded country stretched before them.
As far as the eye could see the great tropical forest loomed up—in
green, brown, red. It was as though all the world were covered with
dense vegetation. The boys turned about.
On the other side was the river, winding through gulches and
hills and stretching out of sight in the distance. Opposite the hill
were the boats, and under trees not far away were the explorers
resting peacefully in the shade.
It was a spectacular view, and Bob and Joe spent several
minutes in silently gazing down.
“No evidence of human habitation anywhere around,” remarked
Bob, trying to single out a settlement somewhere in the distance.
In the vast, silent jungle sound travels far, and realizing this, the
youths shouted to the others, to let them know of their commanding
position.
“Now let’s get down from here and tramp on through the
forest,” said Joe, finding a foothold in the heavy soil.
It was necessary to exercise more care in descending, for the
rocks were pointed and dangerous to step on. A safe place had to be
felt out cautiously.
The youths reached the bottom in a very short time, however,
and followed a narrow trail that wound out of sight.
“Be impossible to cut through this jungle if there were no trails
of any kind,” said Bob, his keen eyes unable to penetrate the tangled
mass of vegetation on either side of them.
“Not without a machete, anyway,” nodded Joe. “Even then it
would be a hard job.”
The youths hiked on until they came to a small stream that
emptied into the river. They sat down on the bank to take in their
surroundings.
On the other side of the stream was a break in the ground that
indicated the presence of a gully—how steep, they did not know.
They resolved to find out as soon as they had rested.
“Unless,” said Joe, “we can’t get across the creek. Never can tell
how many alligators and piranhas have migrated here from the
river.”
He picked up a stone and threw it with all his strength into the
muddy water, hoping to arouse any life that might be lurking
sluggishly out of sight. Once he thought he detected a slight ripple
other than that caused by the stone but was not sure.
“Don’t believe I care to wade it,” backed out Bob. “Wouldn’t feel
funny to have a toe nipped off by a piranha, or worse yet, to be
carried into an alligator’s lair. Suppose we throw a log across for
safety.”
They spent several more minutes sitting on the bank in idleness.
At last Joe got up and looked about the near-by jungle.
“No logs around here,” he called to Bob, who had wandered
along the bank.
Further search was not in vain. A small tree that had been
uprooted by a hurricane lay in a patch of bushes not far away, and it
was carried to the stream and thrown across. Then the youths
began carefully walking along its narrow surface.
Bob reached the other side first, and he warned his friend to be
careful. Joe was, and in a few moments also had crossed the log.
“Now let’s see what’s beyond that ravine,” he said.
They walked over to the edge and then halted abruptly, awe-
stricken and spellbound at the wonderful panorama that stretched
out before them. They were standing at the brink of a two-hundred-
foot canyon, which sloped down and back up to form a perfect U. At
the very bottom was a large grove of huge red flowers, which added
not a little to the beauty of the scene.
“Some view,” breathed Joe, gazing far ahead at the distant
jungle.
Bob nodded. “Bet we can see twenty miles or more,” he said.
“And nothing but dense jungle.”
The youths spent several more minutes in looking off into
space. They could not tear themselves away from the wonderful
view. It seemed almost impossible to come suddenly upon such a
gulch in a land that seemed fairly level.
At last Bob shouldered his rifle as a signal to move on.
“Can’t spend too much time here if we expect to do any more
exploring,” he said, looking at his watch. “They’ll expect us back in
another hour.”
“Where’ll we go next?”
“No difference to me. How about down the hill?”
They hiked down the gradual slope of the canyon, although the
jungle was in places impenetrable.
When about halfway down, Joe stopped suddenly, his face an
ashen gray, his limbs trembling. Bob’s eyes opened wide, and he
clutched his rifle tightly.
The next moment there came a horrid hiss, and the thirty-foot
anaconda lunged forward.
CHAPTER XXII
Lost in the Wilds of Brazil
T HE chief was puzzled by the actions of Bob and Joe, and the
boys realized it, but there was no use trying to explain. It would take
more than signs to convey the idea that more whites were near the
river.
“Suppose we try to get him to go with us,” suggested Joe.
“Think he will?”
“Hard to say. We’ll find out.”
The youths beckoned the Indian to come with them, and they
were surprised to find that he did so without hesitation.
“He probably intends to do anything we ask from now on,” said
Bob. “Our ability to kill wild beasts with fire was too much for him.
Maybe he thinks he’ll die like the tapir if he refuses.”
There was a narrow trail along the bank of the stream, and Bob
led the way down it, followed by Joe and the chief. The boys
intended to make as much time as possible, for they wished to reach
the river as soon as they could. How far away it was, they did not
know. Perhaps a large number of miles.
“If we can just keep the chief with us everything will turn out
fine,” said Bob.
All the rest of that day they trudged on, keeping their rifle ready
for any savage jungle beast that might show itself. The Indian kept
with them tirelessly, and many times he proved of valuable
assistance in pointing out the easiest course through the
underbrush.
Along toward evening they stopped at a large open space that
was devoid of vegetation.
“Better stay here for the night, hadn’t we?” asked Joe.
“Yes,” Bob replied. “You stay here and build a fire while the chief
and I go in search of game. Don’t think you’ll be in any danger. We’ll
be back in a short time.”
Bob and the Indian started out down the bank of the stream,
confident that they would see game sooner or later.
They had not far to go.
At a sharp bend in the trail a small animal, the name of which
Bob did not know, darted out and made for the water.
But it did not get there.
Bang! came the report of the rifle, and the bullet sped straight.
The creature fell dead at once.
This time the Indian did not show signs of fear, for he knew
what was to come. Instead he looked at Bob with awe and wonder
in his eyes.
Back at the clearing they found that Joe had started a large fire.
The warmth of it felt good as the chill of the fast-approaching night
fell.
“You did have some luck, didn’t you?” observed Joe. “Wonder if
it’ll be good eating.”
“Hope so.”
The animal was skinned with Bob’s hunting knife and placed
over the fire to bake. Then the three sat together to witness the
falling of night. As usual it came suddenly, and they huddled closer
to the fire.
In time the animal was thoroughly baked, and then they began
the meal.
Suddenly the chief got up and dashed through the jungle out of
sight, leaving the youths to wonder at this sudden departure.
“Think he’s gone?” asked Joe, trying to catch sight of the Indian
through the dense vegetation.
“Doesn’t seem possible that he’d desert us as abruptly as this,”
replied Bob. “He seemed to be all our friend.”
The youths waited silently, almost convinced that the man had
left for good.
But a moment later he emerged from the jungle as suddenly as
he had disappeared. In his arms were several varieties of what was
evidently wild fruit.
He ran toward the boys with a smile as he glanced first at the
roasted animal and then at the fruit he was carrying. When he
reached the fire he deposited the stuff near, and then sat down to
eat.
“A welcome addition to the meal,” said Bob joyfully. “Takes
these savages to know what all the vast forest contains that’s
nourishing.”
Nevertheless the young men were careful to see that the Indian
ate first before they sampled any of the wild fruit.
“Take no chances,” remarked Joe. “Ten to one he means no
harm, but it’s best to be on the safe side.”
The chief ate of everything, however, and then the boys
followed suit. They found that all of the fruit was delicious, with
flavors that they had never before tasted.
There were large, round melons, like a cross between a
watermelon and a cantaloup. There were bulbs resembling potatoes,
bunches of small bright-colored berries, and wild bananas.
It was a meal unlike any that the boys had ever eaten. They felt
like savages themselves, and were delighted that soon they would
come to the river.
“Won’t it be wonderful to see our party again?” asked Joe,
deeply touched.
“Sure will,” Bob replied. “But we don’t want to be too sure that
everything will turn out all right. Something else may turn up that’s
not expected.”
After the feast the three sat in silence, watching the moon float
silently and majestically over the great jungle.
At last Joe turned to put more fuel on the fire.
“Hadn’t some of us better turn in?” he asked. “We’ve had a
tough time of it today and need rest.”
Bob agreed, and they set about arranging watches.
“I’ll be the first guard,” announced Joe. “You and the chief curl
up by the fire and get some sleep. I’ll call you in a few hours. We’d
better not disturb the Indian tonight.”
Thus it was arranged, and Joe sat idly beside the fire, his rifle
near by.
His watch passed without incident, and at last he tapped Bob on
the back. They changed positions, Joe retiring and Bob keeping a
lookout for intruders.
Despite the fact that Bob had a strange feeling that something
would happen, the night passed peacefully, although the youth was
confident that wild animals were just beyond the zone of firelight.
In the morning Joe and the Indian were up early, preparing to
hike on. The former still did not know where the boys were going or
what their purpose was, but he showed no signs of hesitation.
“We want to see the river today,” remarked Bob, as they again
took up the trail.
“I think we will,” the other youth returned. “We made good time
yesterday, and if the luck continues, we will today.”
All morning they tramped without a stop. They were tired and
exhausted, but did not wish to lose time until necessary.
About noon they came to another clearing, and Bob moved that
they stop for the noon meal.
The chief and Joe went into the jungle a short distance away to
gather wild fruit, which alone was to serve as their meal.
In a short time they returned with a bountiful supply, and then
the feast began.
“Several new additions to our menu today,” remarked Bob, as he
noticed that there were cocoanuts, roots like carrots, and a plant
resembling cane.
The three ate heartily of everything, and then they started on.
“Stream’s getting wider,” observed Bob, several hours later.
“Yes,” returned Joe. “The river shouldn’t be very far away.”
He had scarcely uttered the words when they rounded a sharp
curve and found themselves at the junction with the river.
For a moment the youths could hardly believe their eyes. Here
at last was the thing they had been searching for all these days—the
thing that would lead them to their fathers and the others of the
party. Never had anything looked so good to them.
“At last!” breathed Joe, too delighted for words. “Now let’s hurry
on up to the boats.”
“How do you know we should go up?” demanded Bob. “They
could be easily farther downstream as well.”
“I know it,” was the response. “But it seems to me that I
remember passing this stream several hours before we stopped.”
“All right. Let’s go.”
They had to search quite a while before a path was found that
followed the river.
“If we keep up this good time, we’ll surely see the boats today—
if they’re there to see,” said Bob, as he led the way up the trail.
Notwithstanding this, they hiked on constantly for the remainder
of the afternoon without coming to the explorers’ boats.
“Perhaps if we fire rifle shots it will attract their attention,” said
Joe, and he sent out three shots, repeating at intervals.
“What’s that?” said Joe, raising a hand for silence.
“Thought I heard an answering report,” he said. “But maybe——
Yes, there it is again. And there.”
Two shots had sounded from afar, and at once the boys
responded with Joe’s rifle.
“Now let’s move on upstream,” said Bob. “If we can meet them
halfway it will be all the better.”
The youths again followed the trail, the Indian chief close
behind them. They realized that the answering reports had come
from afar and that it would take no little hiking to get to them.
About every five minutes Joe raised the rifle and fired, each
time receiving an answering shot.
Finally, after an hour’s constant traveling, they heard a crashing
sound in the jungle not far ahead, and they were on the alert at
once.
A moment later Mr. Lewis and Mr. Holton emerged and looked
about.
Their eyes fell on Bob and Joe, and the men rushed forward in
intense relief and thankfulness.
“Boys!” cried Mr. Holton, almost unable to believe his own eyes.
The next instant they were stammering out words of
thanksgiving at finding their sons alive and apparently none the
worse for their experience.
“We didn’t see how you could possibly escape tragedy,” said Mr.
Lewis gravely. “Getting lost in the vast Amazon jungle is a serious
thing, especially when you have no food of any kind with you.”
“All the time we were in doubt as to how we’d come out,” said
Bob. “Worst part of it was that we were afraid to hike far for fear of
getting farther away from the river, but we knew we couldn’t get any
place sitting down.”
“Tell us all about it,” urged Mr. Holton, and the youths related
their experience from start to finish. They told of shooting the
jaguar, of the necessary abandoning of Bob’s rifle, and of the flight
that followed. And at last of coming across the strange tribe of
Indians that was probably the one Professor Bigelow had been
searching for.
“A fearful experience,” breathed Mr. Lewis, when the youths had
finished. “Not many could have had such good luck. If you hadn’t
come across the Indians, your fate would probably have been sealed
by now.”
“But wait,” hesitated Joe, with a sudden recollection. “Here’s the
chief of the tribe we got in with. We finally got him to come with us.”
He glanced around, but the Indian was nowhere in sight.
“Strange,” mused Bob. “He was here a few minutes ago. Could
he have left?”
He called loudly, but it was unnecessary. The man had only
stepped behind a bush, undecided as to whether to come in sight of
the other whites, and at once left his place of concealment and
walked out warily.
Bob and Joe beckoned for him to move up to them. At first he
was uncertain, but finally concluded that it would be safe to venture
nearer.
The boys introduced him as best they could by signs, and
although it was rather awkward, they felt that much of his
uncertainty vanished before the cordial attitude of Mr. Lewis and Mr.
Holton.
“Now we must get to the boats,” Joe’s father said. “Professor
Bigelow will be worried about us, if he is not by now.”
They hiked on up the river, the chief following.
“Won’t the old boy be surprised when he finds that Professor
Bigelow can talk with him!” smiled Joe, as they rounded a long bend.
“That isn’t a strong enough word,” laughed Mr. Holton. “Still,” he
hesitated, “we don’t want to be too sure that this Indian is from the
tribe that the professor was searching for.”
The boats were several miles distant, and it would require
several hours’ traveling to get to them. But the whites were all
overly anxious and made good time.
At last, after passing through a thick grove of palms, they
sighted the boats in the distance.
Professor Bigelow came running up at once, a broad smile of
thankfulness on his bronzed, scholarly face. He gave the boys a
welcome almost as warm as that of Mr. Holton and Mr. Lewis. The
crew, too, took part in the reception and muttered words of joy at
seeing Bob and Joe alive and unharmed. Even the Indians who had
previously attempted desertion joined in, outwardly at least.
“But look here, Professor,” said Bob. “We’ve found the savage
tribe you were searching for and have brought you the chief.”
“What!”
For answer Bob motioned for the Indian, who was standing
several score feet down the path, to come closer. He grudgingly did
so, and the professor was taken completely aback in surprise and
joy. His eyes opened wide, and it was some time before he could
regain his composure.
“How can I ever thank you enough?” he muttered, his eyes on
the sober Indian. “We might have searched for days and days and
then not found the tribe.”
He turned to the chief and said something that the others did
not understand. At once the savage’s face lightened, and he began
chattering so rapidly that the professor had to put up a hand for
silence.
“I’m sorry, but I’m not that familiar with his language,” laughed
the professor. “I think, though, that if he’ll talk slowly I may be able
to understand him. Luckily he’s from the same tribe that Otari told
about.”
Again Professor Bigelow turned to the Indian and this time
asked him to talk more slowly.
He did, and a long conversation followed. It was broken and
awkward, but in the end the professor gained a large amount of
information. There was a smile on his face as he turned to the
others.
“He says he will tell me all I want to know about his people if I
will go with him to his settlement. His people will treat us all right. I
don’t think there is cause to worry about that. What do you think
about going?”
“All right with me,” returned Mr. Holton. “That was one purpose
for coming up here, you know. And the chances are that we’ll find
an abundance of fauna in those remote forests. I’m all for it.”
“Fine,” burst out Professor Bigelow. “Then we’ll go at once. But
first,” he hesitated, “we’ll have to decide who will go and who will
stay with the boats.”
“Why not take the boats with us?” suggested Joe. “The stream
that Bob and I followed to the river is deep, even if it isn’t wide. I
think we can easily paddle through.”
The others gave their approval at once, and they moved on up
to the boats.
They decided to get a lunch first, however, for all were tired
after the day’s strain. The chief was in no special hurry to get back
to the village, as he had often left on long hunting trips alone.
Soon after the meal the provisions that had been taken out
were packed in the boats, and then all climbed in.
“Now let’s make time,” urged Mr. Lewis, and the crew paddled
them upstream.
The afternoon was rapidly wearing away, and before long it
would be night.
At last Mr. Holton called to the crew to stop the boats.
“It’s unsafe to paddle farther,” he said. “Suppose we turn up into
that little bay over there.”
The suggestion was carried out. Then they made camp.
“Hope nothing happens tonight,” said Bob, as he prepared to
turn in for the night.
“I’m with you there,” his chum returned. “Somehow I’ve had
enough thrills for a while.”
But he had no way of knowing how soon action would present
itself in a big way.
The next morning they were up early, preparing to resume the
journey shortly after breakfast. The chief of the strange tribe told
Professor Bigelow that they should reach his village late that day, if
all turned out well.
“I’m not especially anxious to get back among those wild men,”
Bob said aside to his chum. “But we must do all we can to help
Professor Bigelow.”
Late that afternoon the chief said something to the
anthropologist and pointed to a clearly defined trail that wound away
through the heavy vegetation.
“He says that here is where we leave the boats and head for his
village,” the scientist told the others in animated tones.
“Fine!” exclaimed Mr. Lewis, also delighted that the journey had
come to an end. “There’s a place that will act as a harbor,” pointing
to a groove in the shore.
He directed the crew to paddle the boats to land, and as soon
as this was done all climbed out and made the crafts fast to staunch
trees.
Professor Bigelow turned to the savage and conversed for
several minutes. Then he moved to the boats.
“The village isn’t far away,” he said. “It will be safe to leave our
provisions here for the time being.”
As a precaution, however, and also because the naturalists
wished to secure new specimens, they carried their rifles and a good
supply of ammunition.
The chief led the way along the path, the others close at his
heels. The path was so well cut that they had no trouble in walking
along briskly. A half-hour, the Indian said through Professor Bigelow,
would be all the time required to get to the village.
Suddenly the explorers heard a faint screaming and shouting
that came from the village, and at once the chief began chattering
nervously.
Professor Bigelow gave a groan and translated to the others.
“He says that probably a fight is taking place between his tribe
and another,” said the scientist.
“What!” cried Mr. Holton excitedly. “Then that means that we
whites may have to use our rifles after all. Ask him if the other tribe
is using poisoned arrows.”
The savage nodded in affirmation when the question was put
before him, and the whites tightened their grips on their weapons.
“I guess this means that we’re in for some excitement,” Bob
confided to his chum, as the party again followed the trail.
Welcome to our website – the perfect destination for book lovers and
knowledge seekers. We believe that every book holds a new world,
offering opportunities for learning, discovery, and personal growth.
That’s why we are dedicated to bringing you a diverse collection of
books, ranging from classic literature and specialized publications to
self-development guides and children's books.
ebookbell.com